Triple
T30150017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebraska counties |
E766368
|
entity |
| Predicate | haveElectedOffice |
P6491
|
FINISHED |
| Object | county sheriff |
—
|
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: county sheriff | Statement: [Nebraska counties, haveElectedOffice, county sheriff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveElectedOffice Context triple: [Nebraska counties, haveElectedOffice, county sheriff]
-
A.
usesElectedOffice
Indicates that an entity makes use of or leverages an elected public office in relation to another entity or context.
-
B.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
C.
isElectedFor
Indicates that an entity attains a position, role, or office as the result of an election for that specific position.
-
D.
nominatedForOffice
Indicates that an entity has been formally put forward as a candidate to hold a particular office or position.
-
E.
isElectoralOffice
chosen
Indicates that the referenced position or role is an official public office filled through an electoral process.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8eed808190a40b139f12809e30 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:19 p.m.