Triple
T10167489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 116th Street–Columbia University |
E235242
|
entity |
| Predicate | centerTrackUsage |
P34716
|
FINISHED |
| Object | not normally used in revenue service |
—
|
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: not normally used in revenue service | Statement: [116th Street–Columbia University, centerTrackUsage, not normally used in revenue service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerTrackUsage Context triple: [116th Street–Columbia University, centerTrackUsage, not normally used in revenue service]
-
A.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
B.
hasCenterTrackUsage
chosen
Indicates that an entity utilizes or is assigned to a central track within a multi-track system or layout.
-
C.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
trackRecordUsedFor
Indicates that a track record is utilized as a basis or input for some subsequent decision, evaluation, or process.
-
E.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6e016c81909ded2a16b839c405 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.