Triple
T1813565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Rotunda |
E40382
|
entity |
| Predicate | locatedInBuildingType |
P40
|
FINISHED |
| Object | state capitol building |
—
|
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: state capitol building | Statement: [Capitol Rotunda, locatedInBuildingType, state capitol building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBuildingType Context triple: [Capitol Rotunda, locatedInBuildingType, state capitol building]
-
A.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
D.
buildingIncorporatedInto
Indicates that one building has been structurally or functionally integrated into another building as part of a combined or expanded construction.
-
E.
isPublicBuilding
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d884548190a19cf3a6b5ae9d48 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.