Triple
T37647600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allan Shivers |
E937083
|
entity |
| Predicate | assumedOfficeAfter |
P169157
|
FINISHED |
| Object | Beauford H. Jester |
—
|
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: Beauford H. Jester | Statement: [Allan Shivers, assumedOfficeAfter, Beauford H. Jester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumedOfficeAfter Context triple: [Allan Shivers, assumedOfficeAfter, Beauford H. Jester]
-
A.
succeededToOfficeIn
Indicates that one entity assumed or took over an office or position previously held by another entity at a specified time or in a specified succession.
-
B.
tookOfficeAfter
chosen
Indicates that one entity assumed an official position or office at a later time than another entity did.
-
C.
tookOfficeDuring
Indicates that one entity assumed or held an official position within the time period defined by another entity or event.
-
D.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
E.
hasBeenInGovernmentUntil
Indicates that an entity held a government position continuously up to a specified end time or date.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.