Triple
T31119904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky congressional delegation |
E793193
|
entity |
| Predicate | senateChamber |
P87444
|
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: [Kentucky congressional delegation, senateChamber, United States Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: senateChamber Context triple: [Kentucky congressional delegation, senateChamber, United States Senate]
-
A.
chamberOf
Indicates that one entity is a chamber, room, or enclosed space that is part of, contained within, or assigned to another entity.
-
B.
chamberOfCongress
chosen
Indicates that a legislative chamber is a constituent part or house of a specific congress or legislative body.
-
C.
currentRepresentativeChamber
Indicates that an entity currently serves as a representative in a specific legislative chamber.
-
D.
legislativeChamberHoused
Indicates that a particular legislative chamber is located within or accommodated by a specific building or facility.
-
E.
electedChamber
Indicates that an individual has been chosen through an election to serve as a member of a specific legislative chamber.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:04 p.m.