Triple
T5051218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Locomotive Chase |
E113788
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Civil War military operation |
C11608
|
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 Civil War military operation Context triple: [Great Locomotive Chase, instanceOf, American Civil War military operation]
-
A.
event in the American Civil War
chosen
An event in the American Civil War is a specific historical occurrence—such as a battle, campaign, political decision, or social development—that took place between 1861 and 1865 and significantly influenced the course or consequences of the conflict.
-
B.
Civil War site
A Civil War site is a historically significant location where events related to the American Civil War occurred, such as battles, encampments, or military operations, and is preserved or recognized for its cultural and educational value.
-
C.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
D.
American Civil War era site
An American Civil War era site is a historically significant location—such as a battlefield, fort, encampment, prison, or related structure—directly associated with military, political, or social events of the United States Civil War (1861–1865).
-
E.
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.
- F. None of above.
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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:37 p.m.