Triple
T14089421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sullivan, Ohio |
E339083
|
entity |
| Predicate | isSubjectToJurisdiction |
P16807
|
FINISHED |
| Object | Huron County, Ohio |
—
|
NE NERFINISHED |
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: Huron County, Ohio | Statement: [Sullivan, Ohio, isSubjectToJurisdiction, Huron County, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectToJurisdiction Context triple: [Sullivan, Ohio, isSubjectToJurisdiction, Huron County, Ohio]
-
A.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
-
B.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
C.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
D.
hasJurisidiction
Indicates that one entity holds legal authority or control over another entity, area, or matter.
-
E.
existsInJurisdiction
chosen
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.