Triple
T31033448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doc Scurlock |
E790792
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | participant in the Lincoln County War |
C59800
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: participant in the Lincoln County War Context triple: [Doc Scurlock, instanceOf, participant in the Lincoln County War]
-
A.
event in the Lincoln County War
An event in the Lincoln County War is a specific historical incident or occurrence—such as a battle, killing, legal action, or political maneuver—that took place during the 1878–1881 conflict in Lincoln County, New Mexico, and influenced its progression or outcome.
-
B.
event in the Johnson County War
An event in the Johnson County War is a specific historical incident, action, or confrontation involving the conflict between large cattle interests and smaller ranchers and settlers in Johnson County, Wyoming, during the early 1890s.
-
C.
participant in the Mexican–American War
A participant in the Mexican–American War is an individual, military unit, or organized group that actively took part in the planning, fighting, support, or decision-making activities of the 1846–1848 conflict between Mexico and the United States.
-
D.
event in Bleeding Kansas
An event in Bleeding Kansas is a specific historical incident of political conflict or violent confrontation between pro-slavery and anti-slavery forces in the Kansas Territory during the mid-1850s.
-
E.
Old West conflict
A tense and often violent confrontation set in the American frontier era, typically involving cowboys, outlaws, lawmen, and settlers clashing over land, justice, or survival.
- F. None of above. chosen
Provenance (1 batch)
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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.