Triple
T30329555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central City, Colorado |
E771437
|
entity |
| Predicate | inStateRegion |
P96807
|
FINISHED |
| Object | Front Range Urban Corridor |
—
|
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: Front Range Urban Corridor | Statement: [Central City, Colorado, inStateRegion, Front Range Urban Corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inStateRegion Context triple: [Central City, Colorado, inStateRegion, Front Range Urban Corridor]
-
A.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
B.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
C.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
D.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
stateOrRegion
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681c56df8819089afc39435164d29 |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:53 p.m.