Triple
T23020104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Aderholt |
E573137
|
entity |
| Predicate | officeHeldLevel |
P135036
|
FINISHED |
| Object | federal |
—
|
LITERAL FINISHED |
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: federal | Statement: [Robert Aderholt, officeHeldLevel, federal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHeldLevel Context triple: [Robert Aderholt, officeHeldLevel, federal]
-
A.
office held level
chosen
Indicates the hierarchical level or rank at which an office or position is held within an organizational or governmental structure.
-
B.
officeHeldOf
Indicates that a specific office or position is (or was) held by a particular person or entity.
-
C.
officeHeldUnder
Indicates that one entity holds or has held an official position, role, or office under the authority, jurisdiction, or administration of another entity.
-
D.
officeHeldDuring
Indicates that a person occupied a specific official position during a particular time period.
-
E.
aboutOfficeHeld
Indicates that one entity is related to, or provides information about, a specific office or position that is or was held by another entity.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e8324c81908b8868d298af66e1 |
completed | April 29, 2026, 4:07 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.