Triple
T23367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battles of Lexington and Concord |
E464
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the American Revolutionary War |
C380
|
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: event in the American Revolutionary War Context triple: [Battles of Lexington and Concord, instanceOf, event in the American Revolutionary War]
-
A.
colonial-era event
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
B.
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.
-
C.
phase of World War II
A phase of World War II is a distinct, time-bounded period of the conflict characterized by specific strategic objectives, major campaigns, and shifts in military, political, or economic conditions.
-
D.
colonial protest
chosen
Colonial protest refers to the organized resistance and collective actions taken by colonized peoples against imperial rule, policies, and exploitation in pursuit of autonomy, rights, or independence.
-
E.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.