Triple
T11587052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 72nd Street station (IND Eighth Avenue Line) |
E274783
|
entity |
| Predicate | tracksUsedBy |
P27244
|
FINISHED |
| Object | B train |
—
|
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 train | Statement: [72nd Street station (IND Eighth Avenue Line), tracksUsedBy, B train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tracksUsedBy Context triple: [72nd Street station (IND Eighth Avenue Line), tracksUsedBy, B train]
-
A.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over time.
-
B.
trackRecordUsedFor
Indicates that a track record is utilized as a basis or input for some subsequent decision, evaluation, or process.
-
C.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
D.
trackPattern
Indicates that one entity follows, monitors, or records the behavior or state of another according to a defined pattern or sequence.
-
E.
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.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89463360c8190b91228c46bfe2e5f |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.