Triple
T18262715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmon, Illinois |
E437401
|
entity |
| Predicate | nearestUrbanCenterType |
P36605
|
FINISHED |
| Object | micropolitan core city (Sterling, Illinois) |
—
|
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: micropolitan core city (Sterling, Illinois) | Statement: [Harmon, Illinois, nearestUrbanCenterType, micropolitan core city (Sterling, Illinois)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestUrbanCenterType Context triple: [Harmon, Illinois, nearestUrbanCenterType, micropolitan core city (Sterling, Illinois)]
-
A.
nearbyUrbanCenter
chosen
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
B.
nearestCityCenterDistance
Indicates the distance from a given location to the closest city center.
-
C.
nearestTownCenter
Indicates that one location is the closest town center to another specified point or area.
-
D.
nearestIslandCity
Indicates that one city is the closest city located on an island relative to a given reference location or city.
-
E.
nearestTownDistance
Indicates the distance from a given location to the closest town.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff77882c81909774aefc57ccca3e |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.