Triple
T9019959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1111 Avenue of the Americas |
E215694
|
entity |
| Predicate | buildingTypeAtAddress |
P1844
|
FINISHED |
| Object | office skyscraper |
—
|
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: office skyscraper | Statement: [1111 Avenue of the Americas, buildingTypeAtAddress, office skyscraper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingTypeAtAddress Context triple: [1111 Avenue of the Americas, buildingTypeAtAddress, office skyscraper]
-
A.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
D.
buildingFootprint
Indicates the spatial outline or boundary of a building as it meets the ground surface.
-
E.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a421c2c8190abb12c826066fe75 |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.