Triple
T28249971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT (A Division) lines |
E712285
|
entity |
| Predicate | cannotShareTrainsWith |
P168620
|
FINISHED |
| Object | B Division lines |
—
|
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: B Division lines | Statement: [IRT (A Division) lines, cannotShareTrainsWith, B Division lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotShareTrainsWith Context triple: [IRT (A Division) lines, cannotShareTrainsWith, B Division lines]
-
A.
allowsFreightTrains
Indicates that something permits or authorizes the operation or passage of freight trains.
-
B.
notServedByTrain
Indicates that a location or route is not provided with train service or connections.
-
C.
maintainsTrainsFor
Indicates that one entity is responsible for servicing, repairing, or otherwise keeping trains operational for another entity.
-
D.
usesTrainFamily
Indicates that one entity makes use of a train or rail-based transportation system associated with a particular family, category, or group of trains.
-
E.
hasPrivateRailway
Indicates that an entity owns or operates a railway line that is privately controlled rather than part of a public or national rail system.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 11:04 p.m.