Triple
T31150879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Dakota congressional delegation |
E794066
|
entity |
| Predicate | consistsOfChamber |
P33004
|
FINISHED |
| Object | United States Senate |
—
|
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: United States Senate | Statement: [South Dakota congressional delegation, consistsOfChamber, United States Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consistsOfChamber Context triple: [South Dakota congressional delegation, consistsOfChamber, United States Senate]
-
A.
chamberedFor
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
-
B.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
C.
includesChamber
chosen
Indicates that one entity contains or encompasses a specific chamber as part of its structure or composition.
-
D.
chamber2
Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
-
E.
typeOfChamber
Indicates the specific kind or category of chamber that an entity belongs to or is classified as.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:06 p.m.