Triple
T36273993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slim Buttes, Dakota Territory |
E892753
|
entity |
| Predicate | conflictOccurredOn |
P22233
|
FINISHED |
| Object | 1876-09-09 |
—
|
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: 1876-09-09 | Statement: [Slim Buttes, Dakota Territory, conflictOccurredOn, 1876-09-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictOccurredOn Context triple: [Slim Buttes, Dakota Territory, conflictOccurredOn, 1876-09-09]
-
A.
conflictStartTime
chosen
Indicates the specific point in time at which a conflict between entities begins.
-
B.
conflictBeganOver
Indicates that a conflict was initiated due to or in response to a particular cause, issue, or trigger.
-
C.
conflictsOccurIn
Indicates that one or more conflicts take place within, or are situated in, a specified context, location, or setting.
-
D.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
E.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.