Triple
T13287382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toft–Ulsta ferry |
E316477
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Toft |
E316478
|
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: Toft | Statement: [Toft–Ulsta ferry, connects, Toft]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Toft Context triple: [Toft–Ulsta ferry, connects, Toft]
-
A.
Toft
Toft is a rural estate and small settlement in Cheshire, England, known for its historic hall and proximity to the town of Knutsford.
-
B.
Toft
chosen
Toft is a location that serves as one end of the Yell Sound ferry connection in the Shetland Islands, Scotland.
-
C.
Toft
Toft is a small village in South Cambridgeshire, England, situated just west of Cambridge and known for its rural character and close-knit community.
-
D.
Tofte
Tofte is a village in the former Hurum municipality in Norway, known for its coastal location along the Oslofjord and industrial history.
-
E.
Tyvholm
Tyvholm is one of the small Danish islands that form part of the Hirsholmene archipelago in the Kattegat.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99076aeec8190b0cb883ab60d3f6b |
completed | April 11, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f20d7188190bb8643a7e17aba5c |
completed | May 3, 2026, 10:10 a.m. |
Created at: April 9, 2026, 9:27 p.m.