Triple
T37607461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 430 Park Avenue |
E935692
|
entity |
| Predicate | hasFireEscapesOrStairwells |
P154203
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [430 Park Avenue, hasFireEscapesOrStairwells, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFireEscapesOrStairwells Context triple: [430 Park Avenue, hasFireEscapesOrStairwells, true]
-
A.
hasEmergencyStairwells
Indicates that an entity is equipped with one or more stairwells specifically designated and constructed for use during emergencies.
-
B.
hasFireEscapes
chosen
Indicates that a building or structure is equipped with one or more fire escapes as safety exits.
-
C.
hasEmergencyExitShafts
Indicates that an entity is equipped with one or more dedicated emergency exit shafts for evacuation or escape purposes.
-
D.
hasEmergencyExits
Indicates that an entity is equipped with designated emergency exits for use during urgent or hazardous situations.
-
E.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
Created at: May 3, 2026, 4:18 p.m.