Triple
T19828743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatfield–McCoy feud |
E476398
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American history event |
C42669
|
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: American history event Context triple: [Hatfield–McCoy feud, instanceOf, American history event]
-
A.
United States military history event
A United States military history event is a significant occurrence involving U.S. armed forces that influences the nation’s military development, strategy, policy, or historical trajectory.
-
B.
United States legal history event
A United States legal history event is a significant occurrence—such as a court decision, statute, constitutional amendment, or legal controversy—that materially shaped the development, interpretation, or application of American law.
-
C.
event in Native American history
A significant occurrence or series of actions involving Native American peoples that influenced their societies, cultures, territories, or relationships with other groups at a particular time in history.
-
D.
era in United States history
An era in United States history is a distinct time period characterized by particular political, social, economic, and cultural conditions or transformative events that differentiate it from other periods.
-
E.
American history center
An American history center is an educational institution or facility dedicated to collecting, preserving, interpreting, and presenting artifacts, documents, and narratives related to the historical development of the United States.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.