Triple
T24085651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Plum Point Bend |
E596635
|
entity |
| Predicate | commandedByUnion |
P17184
|
FINISHED |
| Object | Charles H. Davis |
—
|
NE NERFINISHED |
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: Charles H. Davis | Statement: [Battle of Plum Point Bend, commandedByUnion, Charles H. Davis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedByUnion Context triple: [Battle of Plum Point Bend, commandedByUnion, Charles H. Davis]
-
A.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
B.
commandedByFrom
Indicates that an entity is under the authority or control of another entity originating from a specified source or location.
-
C.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
D.
commandeeredBy
Indicates that control or possession of something has been forcibly taken over by a particular agent or group.
-
E.
commandedBySide
chosen
Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc28a7cc81909c76d9d992ac21dc |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.