Triple
T10628107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado City |
E250376
|
entity |
| Predicate | usedAsPlaceNameIn |
P20238
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Colorado City, usedAsPlaceNameIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsPlaceNameIn Context triple: [Colorado City, usedAsPlaceNameIn, 19th century]
-
A.
hasPlaceNamesIn
Indicates that something contains, references, or is associated with one or more place names within it.
-
B.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
C.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
D.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
-
E.
hasToponymicUse
chosen
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df9228088190bdd57a95d8671618 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:57 p.m.