Triple
T34842821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of a Thousand Orifices |
E1004386
|
entity |
| Predicate | refersToBuildingHeight |
P41605
|
FINISHED |
| Object | approximately 178 metres |
—
|
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: approximately 178 metres | Statement: [House of a Thousand Orifices, refersToBuildingHeight, approximately 178 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToBuildingHeight Context triple: [House of a Thousand Orifices, refersToBuildingHeight, approximately 178 metres]
-
A.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
B.
buildingHeight
chosen
Indicates the vertical extent or height measurement of a building.
-
C.
refersToBuildingOn
Indicates that one entity explicitly references or designates a specific building as its subject or target.
-
D.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
E.
buildingHeightCharacteristic
Indicates the specific height-related property or measurement that characterizes a building.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4 p.m.