Triple

T35729475
Position Surface form Disambiguated ID Type / Status
Subject Toft ferry terminal E1032712 entity
Predicate connectsTo P845 FINISHED
Object Ulsta ferry terminal
Ulsta ferry terminal is a small port facility on the island of Yell in Shetland, Scotland, serving as a key link in the inter-island ferry network.
E2153334 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: Ulsta ferry terminal | Statement: [Toft ferry terminal, connectsTo, Ulsta ferry terminal]
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: Ulsta ferry terminal
Triple: [Toft ferry terminal, connectsTo, Ulsta ferry terminal]
Generated description
Ulsta ferry terminal is a small port facility on the island of Yell in Shetland, Scotland, serving as a key link in the inter-island ferry network.

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_69f76e10e59081908d81ad9ce22f40b6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a13384bc8190b721f871f8602496 completed May 3, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a387d1b3ac88190995863de0b0358b7 completed June 22, 2026, 12:08 a.m.
NEDg Description generation batch_6a387de3bc6c8190900f31b768ed57c8 completed June 22, 2026, 12:12 a.m.
NED2 Entity disambiguation (via description) batch_6a388040b9b48190b8e3ed03ab9f9bf3 completed June 22, 2026, 12:22 a.m.
Created at: May 3, 2026, 4:05 p.m.