Triple

T26357287
Position Surface form Disambiguated ID Type / Status
Subject Saint Helier Harbour E663098 entity
Predicate operatedBy P86 FINISHED
Object Ports of Jersey
Ports of Jersey is the company responsible for managing and operating Jersey’s main harbours and airport, overseeing maritime and aviation services for the Channel Island.
E1742791 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ports of Jersey | Statement: [Saint Helier Harbour, operatedBy, Ports of Jersey]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ports of Jersey
Triple: [Saint Helier Harbour, operatedBy, Ports of Jersey]
Generated description
Ports of Jersey is the company responsible for managing and operating Jersey’s main harbours and airport, overseeing maritime and aviation services for the Channel Island.

Provenance (5 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69ee8130fc44819094e5ab1da201cd7b completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60ff1090c81908843a08742a1a675 completed May 2, 2026, 2:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12091d339c8190b10a2d626aa3148a completed May 23, 2026, 8:07 p.m.
NEDg Description generation batch_6a120d1f0d84819097d7fefdd8efa7fb completed May 23, 2026, 8:25 p.m.
NED2 Entity disambiguation (via description) batch_6a120d820f9c819082ba717fe783cf50 completed May 23, 2026, 8:26 p.m.
Created at: April 26, 2026, 10:49 p.m.