Triple
T351401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Room |
E7449
|
entity |
| Predicate | ceilingHeight |
P11120
|
FINISHED |
| Object | double-height ceiling |
—
|
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: double-height ceiling | Statement: [East Room, ceilingHeight, double-height ceiling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceilingHeight Context triple: [East Room, ceilingHeight, double-height ceiling]
-
A.
roofHeight
Indicates the vertical distance or elevation of a roof relative to a reference level or structure.
-
B.
architecturalHeight
Indicates the measured vertical extent of a structure based on its architectural design, typically from the lowest significant level to the highest architecturally integral point, excluding non-architectural elements like antennas or masts.
-
C.
floorCount
Indicates the number of floors or levels that a building or structure has.
-
D.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
E.
heightOfDome
Indicates the measured vertical extent or elevation of a dome structure from its base to its highest point.
- F. None of above. chosen
Provenance (4 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7df63c8190b7cd1bcfdfd96187 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.