Triple
T34911983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rico, Colorado |
E1006895
|
entity |
| Predicate | hasCountyLevelJurisdiction |
P62083
|
FINISHED |
| Object | Dolores County |
E1760482
|
NE 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: Dolores County | Statement: [Rico, Colorado, hasCountyLevelJurisdiction, Dolores County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyLevelJurisdiction Context triple: [Rico, Colorado, hasCountyLevelJurisdiction, Dolores County]
-
A.
hasCountyLevelCity
Indicates that an entity (typically a region or province) includes or administers one or more cities that hold county-level administrative status.
-
B.
countyJurisdiction
chosen
Indicates that one entity (typically a government body or authority) has legal or administrative jurisdiction over a specific county.
-
C.
hasCountyRights
Indicates that an entity possesses the legal or administrative rights, privileges, or status associated with a county-level jurisdiction.
-
D.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
E.
haveTerritorialJurisdiction
Indicates that one entity possesses official legal authority or control over activities and matters within a specified geographic area.
- F. None of above.
Provenance (4 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786f097fc8190ab2b442bd6c7c556 |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.