Triple
T33814500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chet Edwards |
E866632
|
entity |
| Predicate | precededBy (TX-11) |
P163874
|
FINISHED |
| Object | Marvin Leath |
—
|
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: Marvin Leath | Statement: [Chet Edwards, precededBy (TX-11), Marvin Leath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededBy (TX-11) Context triple: [Chet Edwards, precededBy (TX-11), Marvin Leath]
-
A.
precededByInProtocol
Indicates that one step, action, or element in a protocol occurs earlier in the defined sequence than another, directly preceding it in order.
-
B.
precededByAsRepresentativeForTX30
Indicates that one entity previously served as the representative for Texas’s 30th district before another entity took on that same representative role.
-
C.
precededByInPosition
chosen
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
-
D.
usedToPrecede
Indicates that one entity regularly or habitually came before another in time or sequence in the past.
-
E.
precededBySpecial
Indicates that one event or entity occurs immediately before another in a context marked as special or exceptional compared to normal ordering.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:46 a.m.