Triple
T2812137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraser Canyon War |
E54194
|
entity |
| Predicate | combatantsDescription |
P21502
|
FINISHED |
| Object | Indigenous warriors and armed miners |
—
|
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: Indigenous warriors and armed miners | Statement: [Fraser Canyon War, combatantsDescription, Indigenous warriors and armed miners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantsDescription Context triple: [Fraser Canyon War, combatantsDescription, Indigenous warriors and armed miners]
-
A.
combatantsIncluded
chosen
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
B.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
C.
mainCombatant
Indicates that the subject is the primary participant or leading party in a conflict, battle, or combat situation involving the object.
-
D.
combatant2Commander
Indicates that a combatant serves under the authority or command of a specific commander.
-
E.
combatantLanguage
Indicates the language used by a combatant in a conflict or competitive interaction.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde354a5881908cd3d545f7dda81c |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.