Triple
T7913169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flushing Main Street station |
E183748
|
entity |
| Predicate | hasOverheadStructures |
P79748
|
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: [Flushing Main Street station, hasOverheadStructures, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverheadStructures Context triple: [Flushing Main Street station, hasOverheadStructures, yes]
-
A.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
B.
hasIslandSuperstructure
Indicates that one entity possesses or includes an island-like elevated central structure as a distinct component or feature.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasCommercialInfrastructure
Indicates that an entity possesses or is equipped with facilities, systems, or structures that support commercial or business activities.
-
E.
remainingStructuresUsedFor
Indicates that the remaining structures of an entity are utilized for a specified purpose or function.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a748f4c8190bcd868de2fcf0b3a |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:04 p.m.