Triple
T27409231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 191st Street |
E692094
|
entity |
| Predicate | platformDirection |
P158144
|
FINISHED |
| Object | northbound platform |
—
|
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: northbound platform | Statement: [191st Street, platformDirection, northbound platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformDirection Context triple: [191st Street, platformDirection, northbound platform]
-
A.
platform1Direction
chosen
Indicates the direction or orientation associated with the first platform in a given context.
-
B.
platform2Direction
Indicates the direction or orientation associated with a second platform in a given context.
-
C.
platformUsedFor
Indicates that one entity serves as the platform, medium, or environment utilized to perform, host, or support the activities of another entity.
-
D.
platformUsed
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
-
E.
performanceOrientation
Indicates a relationship where an entity is characterized by a focus on achieving high performance, results, or measurable outcomes in its activities or behavior.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 12:31 p.m.