Triple
T1859036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellis County, Oklahoma |
E41771
|
entity |
| Predicate | largestSettlementType |
P14278
|
FINISHED |
| Object | town |
—
|
LITERAL 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: town | Statement: [Ellis County, Oklahoma, largestSettlementType, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestSettlementType Context triple: [Ellis County, Oklahoma, largestSettlementType, town]
-
A.
humanSettlementType
chosen
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
B.
largestUrbanConcentrationIn
Indicates that an entity represents the biggest or most populous urban area located within a specified geographic region.
-
C.
largestCity
Indicates that one city is the most populous or significant urban center within a specified region or entity.
-
D.
isLargestCityIn
Indicates that one city has the greatest population or size compared to all other cities within a specified region or administrative area.
-
E.
largestCommunityIn
Indicates that one community is the largest (by some defined measure, such as population or size) among all communities within a given area or entity.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.