Triple
T30993203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyoming Stock Growers Association |
E789720
|
entity |
| Predicate | conflictTypeInvolvement |
P1397
|
FINISHED |
| Object | range war |
—
|
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: range war | Statement: [Wyoming Stock Growers Association, conflictTypeInvolvement, range war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypeInvolvement Context triple: [Wyoming Stock Growers Association, conflictTypeInvolvement, range war]
-
A.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
laterConflictInvolvement
Indicates that an entity becomes involved in a conflict at a subsequent time relative to another referenced event or involvement.
-
C.
conflictsInvolvedIn
Indicates that an entity participates as a party or actor in one or more conflicts.
-
D.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
E.
conflictExperience
Indicates that an entity has undergone or been involved in a conflict, such as a dispute, struggle, or confrontation.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 8:56 p.m.