Triple
T25161868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 79th Street |
E626459
|
entity |
| Predicate | hasExpressTracksBypassed |
P117004
|
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: [79th Street, hasExpressTracksBypassed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressTracksBypassed Context triple: [79th Street, hasExpressTracksBypassed, yes]
-
A.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
B.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
C.
hasExpressPassAccess
Indicates that an entity is granted special expedited or priority access, typically bypassing standard queues or procedures.
-
D.
expressTracksBypass
chosen
Indicates that express train tracks pass around or avoid a particular location or section rather than going directly through it.
-
E.
hasCenterExpressTracks
Indicates that the subject location or facility contains express railway tracks running through its central area or core.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:31 a.m.