Triple
T36497902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 40th Street–Lowery Street |
E899241
|
entity |
| Predicate | expressTrackUsage |
P27244
|
FINISHED |
| Object | used by peak-direction 7 express trains |
—
|
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: used by peak-direction 7 express trains | Statement: [40th Street–Lowery Street, expressTrackUsage, used by peak-direction 7 express trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressTrackUsage Context triple: [40th Street–Lowery Street, expressTrackUsage, used by peak-direction 7 express trains]
-
A.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
B.
tracksUsage
Indicates that one entity monitors, records, or keeps a log of how another entity is used over time.
-
C.
usesTrackage
chosen
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
trackUsed
Indicates that a particular track (such as a route, path, or media track) has been utilized or selected in a given context.
-
E.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.