Triple
T33171586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherman County, Kansas |
E849046
|
entity |
| Predicate | countySeatPopulationCenter |
P383
|
FINISHED |
| Object | Goodland, Kansas |
E1270749
|
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: Goodland, Kansas | Statement: [Sherman County, Kansas, countySeatPopulationCenter, Goodland, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countySeatPopulationCenter Context triple: [Sherman County, Kansas, countySeatPopulationCenter, Goodland, Kansas]
-
A.
hasCountySeatPopulation
Indicates that a county is associated with a county seat whose population has a specified size or value.
-
B.
countySeat
chosen
Indicates that one place serves as the administrative center or capital of a county.
-
C.
countyPopulationContext
Indicates the contextual population information associated with a specific county, such as its size, demographics, or population-related status within a given scope or time.
-
D.
isPopulationCenter
Indicates that a location functions as a primary hub where people live, work, and concentrate in significant numbers.
-
E.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbaee1208190bd87256d4ad40fdb |
completed | June 23, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: May 1, 2026, 1:29 a.m.