Triple
T32284129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champ Clark |
E824777
|
entity |
| Predicate | heldSeatFor |
P15391
|
FINISHED |
| Object | Missouri's 12th congressional district |
—
|
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: Missouri's 12th congressional district | Statement: [Champ Clark, heldSeatFor, Missouri's 12th congressional district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldSeatFor Context triple: [Champ Clark, heldSeatFor, Missouri's 12th congressional district]
-
A.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
B.
hasSeatAt
chosen
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
C.
seatOwnedBy
Indicates that a particular seat is possessed or held in ownership by a specific entity.
-
D.
seatWinner
Indicates that a particular candidate or party has won a specific seat (e.g., in an election or contest).
-
E.
establishedAsSeatIn
Indicates that an entity was officially designated or recognized as the administrative or official seat of another entity at a particular time or within a specific context.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bccd1aa88190882a5dbb8100ca1e |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:43 a.m.