Triple
T32107031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diefenbunker National Historic Site of Canada |
E820010
|
entity |
| Predicate | numberOfStoreysUnderground |
P203452
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Diefenbunker National Historic Site of Canada, numberOfStoreysUnderground, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfStoreysUnderground Context triple: [Diefenbunker National Historic Site of Canada, numberOfStoreysUnderground, 4]
-
A.
numberOfUndergroundStations
Indicates the total count of underground (subway/metro) stations associated with a given entity.
-
B.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
C.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
D.
hasUndergroundLength
Indicates the extent of an object or structure that lies below ground level, measured as its underground length.
-
E.
percentageUnderground
Indicates the proportion of an entity or its extent that is located below ground level.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
| PDg | Predicate description generation | batch_6a01839a63a48190a59a6c4464db0eea |
completed | May 11, 2026, 7:22 a.m. |
Created at: May 1, 2026, 12:27 a.m.