Triple
T38428348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sand Creek, Colorado Territory |
E903725
|
entity |
| Predicate | preAttackStatusOfCamp |
P167400
|
FINISHED |
| Object | Cheyenne and Arapaho encampment |
—
|
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: Cheyenne and Arapaho encampment | Statement: [Sand Creek, Colorado Territory, preAttackStatusOfCamp, Cheyenne and Arapaho encampment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preAttackStatusOfCamp Context triple: [Sand Creek, Colorado Territory, preAttackStatusOfCamp, Cheyenne and Arapaho encampment]
-
A.
preAttackCondition
Indicates the circumstances or requirements that must be satisfied before an attack can be initiated.
-
B.
preBattleAction
Indicates an action or set of actions performed by an entity immediately before a battle or combat event.
-
C.
preFightStatusOfAli
Indicates the condition or state Ali was in immediately before a fight or combat event.
-
D.
combatantsStatusBefore
chosen
Indicates the condition or status of the involved combatants immediately prior to a combat or conflict event.
-
E.
statusOfCityBeforeBattle
Indicates the condition or situation a city was in immediately prior to a specific battle.
- 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_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.