Triple
T27432745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breckenridge County, Kansas |
E690689
|
entity |
| Predicate | spellingVariantOfName |
P457
|
FINISHED |
| Object | Breckinridge County, Kansas |
—
|
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: Breckinridge County, Kansas | Statement: [Breckenridge County, Kansas, spellingVariantOfName, Breckinridge County, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spellingVariantOfName Context triple: [Breckenridge County, Kansas, spellingVariantOfName, Breckinridge County, Kansas]
-
A.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
B.
nameHasVariant
Indicates that an entity’s name has an alternative or variant form.
-
C.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
E.
EuropeanNameVariant
Indicates that one name is a variant or alternative form of another name as used in a European language or cultural context.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d5bcfd08190a92bf6213a07769e |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:42 p.m.