Triple
T32065473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skokomish, Washington |
E818866
|
entity |
| Predicate | hasPrimaryGovernment |
P150630
|
FINISHED |
| Object | Mason 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: Mason County government | Statement: [Skokomish, Washington, hasPrimaryGovernment, Mason County government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryGovernment Context triple: [Skokomish, Washington, hasPrimaryGovernment, Mason County government]
-
A.
hasGovernmentTypeCountry
Indicates that a country possesses or is characterized by a particular form or type of government.
-
B.
hasPrimaryNation
Indicates that one entity is designated as the main or principal nation associated with another entity.
-
C.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
-
D.
hasFormedGovernmentType
Indicates that an entity has established or adopted a particular type or system of government.
-
E.
hasGovernmentServicesProvidedBy
chosen
Indicates that one entity receives its governmental services from, or is administratively served 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
Created at: May 1, 2026, 12:22 a.m.