Triple
T10370892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson County, Wyoming |
E244377
|
entity |
| Predicate | hasHistoricConflict |
P37642
|
FINISHED |
| Object | range wars between cattlemen and settlers |
—
|
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 wars between cattlemen and settlers | Statement: [Johnson County, Wyoming, hasHistoricConflict, range wars between cattlemen and settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricConflict Context triple: [Johnson County, Wyoming, hasHistoricConflict, range wars between cattlemen and settlers]
-
A.
conflictHistory
chosen
Indicates a history of conflict or antagonistic interactions that have occurred between the related entities.
-
B.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
C.
hasMonthOfConflict
Indicates that a conflict is associated with, occurs in, or is characterized by a specific calendar month.
-
D.
opponentInHistoricalConflict
Indicates that two entities stood on opposing sides in a specific historical conflict or war.
-
E.
hasHistoricRivalry
Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9737cfc81909d6302bd4177d186 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.