Triple
T1098592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Morgan |
E24325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Revolutionary War veteran |
C4839
|
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 Revolutionary War veteran Context triple: [Daniel Morgan, instanceOf, American Revolutionary War veteran]
-
A.
American colonial soldier
chosen
An American colonial soldier is an armed militiaman or regular enlisted in the British American colonies who participated in local defense, frontier warfare, and major conflicts such as the French and Indian War and the American Revolutionary War.
-
B.
British Army veteran
A British Army veteran is a former member of the United Kingdom's land warfare force who has completed their service, whether in peacetime or conflict, and is recognized for their military contribution.
-
C.
World War II veteran
A World War II veteran is an individual who served in the armed forces of any nation during the global conflict of 1939–1945, participating in military operations or support roles related to the war.
-
D.
American Revolutionary War site
An American Revolutionary War site is a historically significant location where events related to the American struggle for independence—such as battles, encampments, political actions, or key decisions—took place and are preserved or commemorated today.
-
E.
Revolutionary War site
A Revolutionary War site is a historically significant location where events, battles, encampments, or strategic activities related to the American Revolutionary War took place and are preserved or interpreted today.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:43 p.m.