Triple
T22818629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 28th Street station (IRT Lexington Avenue Line) |
E565166
|
entity |
| Predicate | mezzanine |
P3741
|
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: [28th Street station (IRT Lexington Avenue Line), mezzanine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mezzanine Context triple: [28th Street station (IRT Lexington Avenue Line), mezzanine, yes]
-
A.
hasMezzanine
chosen
Indicates that one entity includes or is equipped with a mezzanine level in relation to another entity.
-
B.
ceiling
Indicates that one entity is the smallest value that is greater than or equal to another value, typically representing a rounding-up operation.
-
C.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
D.
mineLayer
Indicates that an entity is responsible for placing or deploying mines in an area or along a route.
-
E.
chamberSupportedBy
Indicates that a chamber is physically held up, carried, or structurally sustained by another object or structure.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dce762c8190934fb921f942c9fd |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.