Triple
T22320662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 77th Street |
E551773
|
entity |
| Predicate | hasNorthboundPlatform |
P147727
|
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: [77th Street, hasNorthboundPlatform, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthboundPlatform Context triple: [77th Street, hasNorthboundPlatform, yes]
-
A.
hasNorthboundServicesTo
Indicates that an entity provides or supports services that travel or operate in a northbound direction to another location or entity.
-
B.
hasPlatformEdge
Indicates that an entity possesses or includes a boundary or edge associated with a platform.
-
C.
hasSouthboundServicesTo
Indicates that a location provides transportation services traveling in a generally southward direction to another location.
-
D.
hasPlatformNumber
Indicates that a location or service is associated with a specific platform identified by a platform number.
-
E.
hasBayPlatforms
Indicates that a station or terminal is equipped with bay platforms, where tracks end in a dead-end configuration and trains enter and exit from the same direction.
- F. None of above. chosen
Provenance (4 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15763bf0881908d859f85b4a6ce28 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:42 p.m.