Triple
T9047866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catthorpe Interchange |
E216802
|
entity |
| Predicate | formerLayout |
P51587
|
FINISHED |
| Object | partially at-grade junction |
—
|
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: partially at-grade junction | Statement: [Catthorpe Interchange, formerLayout, partially at-grade junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLayout Context triple: [Catthorpe Interchange, formerLayout, partially at-grade junction]
-
A.
formerlyConfiguration
chosen
Indicates that one entity was previously configured or arranged in the state or setup represented by the other entity, but is no longer so.
-
B.
formerRepresentation
Indicates that one entity previously served as the representative (e.g., legal, political, or organizational) of another entity, but no longer holds that role.
-
C.
formerSurface
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
D.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
E.
formerLine
Indicates that an entity previously served as a particular transit or service line but no longer does so.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b5022c88190ab6b6de3c3830a41 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.