Triple
T29552792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee County, Oklahoma |
E749819
|
entity |
| Predicate | hasCountyAbbreviation |
P202387
|
FINISHED |
| Object | Cherokee Co., OK |
—
|
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: Cherokee Co., OK | Statement: [Cherokee County, Oklahoma, hasCountyAbbreviation, Cherokee Co., OK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyAbbreviation Context triple: [Cherokee County, Oklahoma, hasCountyAbbreviation, Cherokee Co., OK]
-
A.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
B.
hasCountyCodeType
Indicates that an entity is associated with a specific type or classification of county code.
-
C.
hasPostalAbbreviationState
Indicates that a state is associated with a specific standardized postal abbreviation.
-
D.
hasCountyEquivalentStatus
Indicates that an entity holds an administrative or legal status equivalent to that of a county within a given jurisdiction.
-
E.
hasPostalAddressCounty
Indicates that an entity’s postal address is located within a specified county.
- F. None of above. chosen
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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a007899cadc8190a04edd503eaf6514 |
completed | May 10, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a0078493e088190b0c5047cbe75d304 |
completed | May 10, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_6a00789927708190b031d3a9d5f4f68e |
completed | May 10, 2026, 12:22 p.m. |
Created at: April 28, 2026, 5:13 p.m.