Triple
T10001491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wakefield–241st Street |
E197337
|
entity |
| Predicate | hasCenterTrack |
P74866
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wakefield–241st Street, hasCenterTrack, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCenterTrack Context triple: [Wakefield–241st Street, hasCenterTrack, yes]
-
A.
hasCenterTrackUsage
Indicates that an entity utilizes or is assigned to a central track within a multi-track system or layout.
-
B.
hasCenterExpressTracks
chosen
Indicates that the subject location or facility contains express railway tracks running through its central area or core.
-
C.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
D.
hasCenterColor
Indicates that an entity possesses a central region whose color is specified or characterized.
-
E.
hasEarlyCenter
Indicates that an entity possesses or is associated with a primary focal point, hub, or center that occurs or is established earlier than others in time or sequence.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8f50888190b2f1c5240cb58e4f |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.