Triple
T35547574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Boonville |
E1027260
|
entity |
| Predicate | effectOnMissouri |
P173249
|
FINISHED |
| Object | helped keep Missouri under Union control |
—
|
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: helped keep Missouri under Union control | Statement: [Battle of Boonville, effectOnMissouri, helped keep Missouri under Union control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnMissouri Context triple: [Battle of Boonville, effectOnMissouri, helped keep Missouri under Union control]
-
A.
impactOnStates
chosen
Indicates the effect or influence that one entity, event, or condition has on the status, condition, or behavior of one or more states.
-
B.
affectedU.S.State
Indicates that a particular U.S. state is impacted or influenced by a specified event, condition, or entity.
-
C.
effectOnHawaii
Indicates the impact or influence that something has on Hawaii.
-
D.
effectOnUnitedStates
Indicates the impact, influence, or consequences that something has on the United States.
-
E.
effectOnFederalPower
Indicates how an action, decision, or condition changes, limits, or expands the authority or powers of the federal government.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:04 p.m.