Triple
T30361553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sailor Creek |
E772299
|
entity |
| Predicate | commandedBy (Union) |
P1407
|
FINISHED |
| Object | Philip H. Sheridan |
—
|
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: Philip H. Sheridan | Statement: [Battle of Sailor Creek, commandedBy (Union), Philip H. Sheridan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedBy (Union) Context triple: [Battle of Sailor Creek, commandedBy (Union), Philip H. Sheridan]
-
A.
commandedBy
chosen
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.
commandedAs
Indicates that one entity held authority over another and issued orders or directives to be carried out.
-
D.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 7:58 p.m.