Triple
T31425013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basement of the White House |
E801636
|
entity |
| Predicate | architecturalLevelOf |
P164815
|
FINISHED |
| Object | Executive Residence of the White House |
—
|
NE NERFINISHED |
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: Executive Residence of the White House | Statement: [Basement of the White House, architecturalLevelOf, Executive Residence of the White House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalLevelOf Context triple: [Basement of the White House, architecturalLevelOf, Executive Residence of the White House]
-
A.
architectureLevel
chosen
Indicates the relative layer or tier an entity occupies within an architectural structure or system design.
-
B.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
C.
buildingLevels
Indicates the number of floors or levels that a building has.
-
D.
architecturalPhilosophy
Indicates the guiding theoretical or conceptual approach that shapes how something is designed or structured architecturally.
-
E.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 30, 2026, 8:52 p.m.