Triple
T22350432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 53rd Street |
E552511
|
entity |
| Predicate | mezzanineLocation |
P143279
|
FINISHED |
| Object | above platforms |
—
|
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: above platforms | Statement: [53rd Street, mezzanineLocation, above platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mezzanineLocation Context triple: [53rd Street, mezzanineLocation, above platforms]
-
A.
hasMezzanine
Indicates that one entity includes or is equipped with a mezzanine level in relation to another entity.
-
B.
roofLocation
Indicates that one entity is located on, at, or forming the roof of another entity.
-
C.
mineLocation
Indicates that a specified location is the site where a particular mine (e.g., resource extraction or explosive device) is situated.
-
D.
hallLocatedNear
Indicates that a hall is situated close to another specified place or entity in physical space.
-
E.
locationInArchitecture
chosen
Indicates the spatial position or placement of one architectural element or feature within or relative to another architectural structure or context.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1579ad6708190ba4af97a02d0758d |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.