Triple
T4017222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Senate |
E91191
|
entity |
| Predicate | buildingTypeOfChamber |
P53465
|
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: [Indiana Senate, buildingTypeOfChamber, state capitol building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingTypeOfChamber Context triple: [Indiana Senate, buildingTypeOfChamber, state capitol building]
-
A.
buildingStyleOfChamber
Indicates the architectural style or design type associated with a particular chamber.
-
B.
chamberType
Indicates the specific kind or category of chamber associated with an entity (e.g., room, compartment, or enclosed space type).
-
C.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
D.
typicalChamber
Indicates that something is a standard or characteristic chamber associated with a given context or entity.
-
E.
definesChamber
Indicates that one entity specifies or establishes the structure, properties, or identity of a particular chamber.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa85ac881909e46fb3d76a794af |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:35 p.m.