Triple
T12631703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humboldt County Commission |
E301657
|
entity |
| Predicate | hasGoverningBodyRole |
P81461
|
FINISHED |
| Object | legislative |
—
|
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: legislative | Statement: [Humboldt County Commission, hasGoverningBodyRole, legislative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoverningBodyRole Context triple: [Humboldt County Commission, hasGoverningBodyRole, legislative]
-
A.
hasGoverningRole
Indicates that one entity holds an official position of authority, control, or governance over another entity or domain.
-
B.
governingBodySupportRole
Indicates that one entity plays a supporting or auxiliary role in relation to the governing body of another entity.
-
C.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
-
D.
hasLocalGovernanceRole
chosen
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
E.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.