Triple
T13461128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnehaha County Commission |
E311367
|
entity |
| Predicate | memberOfGovernmentType |
P62479
|
FINISHED |
| Object | county government |
—
|
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 government | Statement: [Minnehaha County Commission, memberOfGovernmentType, county government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfGovernmentType Context triple: [Minnehaha County Commission, memberOfGovernmentType, county government]
-
A.
basedInGovernmentType
chosen
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
B.
inGovernmentFrom
Indicates that an entity holds or has held a government position or role starting from a specified point in time.
-
C.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
D.
governingBodyMember
Indicates that an entity serves as a member of the official governing body of another entity.
-
E.
memberOfPoliticalInstitution
Indicates that an entity belongs to, serves in, or holds membership within a specific political body or institution.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0d95fc81909d9f73d5315dc7b4 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03dcd0c8190a8927eb4eaad1c45 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.