Triple
T24628994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldham and Rochdale Line |
E609618
|
entity |
| Predicate | formerModeOnCorridor |
P156810
|
FINISHED |
| Object | heavy rail |
—
|
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: heavy rail | Statement: [Oldham and Rochdale Line, formerModeOnCorridor, heavy rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerModeOnCorridor Context triple: [Oldham and Rochdale Line, formerModeOnCorridor, heavy rail]
-
A.
corridorFunction
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
-
B.
formerUseOfCorridor
Indicates that a corridor was previously used for a particular purpose or function, but is no longer used in that way.
-
C.
formerNameOfCorridor
Indicates that one corridor previously had a different name, which is now the current name of another corridor.
-
D.
firstCorridorOpened
Indicates that the first corridor in a sequence or structure has been opened or made accessible.
-
E.
followedCorridor
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
- F. None of above. chosen
Provenance (4 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:32 a.m.