Triple
T33814501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chet Edwards |
E866632
|
entity |
| Predicate | succeededBy (TX-11) |
P200848
|
FINISHED |
| Object | Charles W. Stenholm |
—
|
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: Charles W. Stenholm | Statement: [Chet Edwards, succeededBy (TX-11), Charles W. Stenholm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededBy (TX-11) Context triple: [Chet Edwards, succeededBy (TX-11), Charles W. Stenholm]
-
A.
succeededByTicker
Indicates that one entity is directly followed or replaced by another entity in a sequence of ticker symbols.
-
B.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
C.
succeededByAsRepresentativeForTX30
Indicates that one entity was followed in time by another entity as the official representative for Texas’s 30th congressional district.
-
D.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
E.
succeededByTicket
Indicates that one ticket directly follows and replaces another ticket in sequence.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
| PDg | Predicate description generation | batch_69ffb1f001948190a63c493b596a97b9 |
completed | May 9, 2026, 10:15 p.m. |
Created at: May 1, 2026, 1:46 a.m.