Triple
T33006355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas–Belfast |
E844509
|
entity |
| Predicate | terminusOnOtherEnd |
P159755
|
FINISHED |
| Object | Belfast |
—
|
NE NERFINISHED |
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: Belfast | Statement: [Douglas–Belfast, terminusOnOtherEnd, Belfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusOnOtherEnd Context triple: [Douglas–Belfast, terminusOnOtherEnd, Belfast]
-
A.
terminusAdjacentTo
Indicates that one terminus (end point) of a route, line, or feature is directly next to or immediately bordering another terminus.
-
B.
terminusTowards
chosen
Indicates that one entity serves as the endpoint or directional terminus oriented toward another entity.
-
C.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
D.
terminusConnectsTo
Indicates that a transportation route’s endpoint is directly linked or transitions to another route, line, or terminal.
-
E.
locatedAtTerminusOf
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
- F. None of above.
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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 1:23 a.m.