Triple
T38428344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sand Creek, Colorado Territory |
E903725
|
entity |
| Predicate | memorialSiteDesignationYear |
P105575
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Sand Creek, Colorado Territory, memorialSiteDesignationYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialSiteDesignationYear Context triple: [Sand Creek, Colorado Territory, memorialSiteDesignationYear, 2007]
-
A.
federalDesignationYear
Indicates the year in which an entity was officially granted a federal designation or status.
-
B.
heritageDesignationYear
Indicates the year in which something was formally granted a particular heritage designation or status.
-
C.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
-
D.
NationalHistoricSiteDesignationYear
Indicates the year in which a place or property was officially designated as a National Historic Site.
-
E.
yearDesignated
chosen
Indicates the specific year in which something was formally designated, assigned, or given an official status.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:31 p.m.