Triple
T36454571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 116th Street (planned) |
E898115
|
entity |
| Predicate | hasPlannedPlatformType |
P842
|
FINISHED |
| Object | underground station |
—
|
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: underground station | Statement: [116th Street (planned), hasPlannedPlatformType, underground station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedPlatformType Context triple: [116th Street (planned), hasPlannedPlatformType, underground station]
-
A.
hasPlatformType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
B.
hasPlannedTerminalType
Indicates that an entity is associated with a specific type of terminal that is intended or scheduled to be used in the future.
-
C.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
D.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
-
E.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 3, 2026, 4:10 p.m.