Triple
T2154153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York railway station |
E47847
|
entity |
| Predicate | formerStructureType |
P16344
|
FINISHED |
| Object | terminus |
—
|
LITERAL 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: terminus | Statement: [York railway station, formerStructureType, terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerStructureType Context triple: [York railway station, formerStructureType, terminus]
-
A.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
B.
formerType
chosen
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
C.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
D.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
E.
replacedStructureType
Indicates that one structure type has been substituted or superseded by another structure type.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe64fdf081909a5ea6818bddd18c |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.