Triple
T28970342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blair Mountain, West Virginia |
E734252
|
entity |
| Predicate | conflictTypeAtSite |
P1397
|
FINISHED |
| Object | armed labor conflict |
—
|
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: armed labor conflict | Statement: [Blair Mountain, West Virginia, conflictTypeAtSite, armed labor conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypeAtSite Context triple: [Blair Mountain, West Virginia, conflictTypeAtSite, armed labor conflict]
-
A.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
conflictTypeManaged
Indicates that a conflict has been addressed or handled through some form of management or resolution process.
-
C.
conflictTypeLed
Indicates that one type or category of conflict directly resulted in, triggered, or gave rise to another specified outcome or situation.
-
D.
conflictLocation
Indicates the place or geographic area where a conflict, dispute, or confrontation occurs or is centered.
-
E.
drivesConflictType
Indicates a relationship where one factor or entity is the primary cause or driver of a particular type or category of conflict.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 9:05 a.m.