Triple
T38428327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sand Creek, Colorado Territory |
E903725
|
entity |
| Predicate | eventNameAtSite |
P36296
|
FINISHED |
| Object | Sand Creek Massacre |
—
|
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: Sand Creek Massacre | Statement: [Sand Creek, Colorado Territory, eventNameAtSite, Sand Creek Massacre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventNameAtSite Context triple: [Sand Creek, Colorado Territory, eventNameAtSite, Sand Creek Massacre]
-
A.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
B.
eventLocationOfNotableActivity
chosen
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
hostedEventsNearby
Indicates that an entity has organized or is responsible for events occurring within a nearby geographic area relative to another reference point.
-
E.
eventSchedule
Indicates that an event is associated with a specific planned time, date, or sequence within a schedule.
- 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_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.