Triple
T33430917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 22 September 1914 |
E856127
|
entity |
| Predicate | commanderOfU9 |
P64599
|
FINISHED |
| Object | Otto Weddigen |
—
|
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: Otto Weddigen | Statement: [Action of 22 September 1914, commanderOfU9, Otto Weddigen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderOfU9 Context triple: [Action of 22 September 1914, commanderOfU9, Otto Weddigen]
-
A.
UnionCommanderOfAssault
Indicates that the subject served as the commanding Union officer in charge of a specific military assault.
-
B.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
C.
commanderOnBoard
chosen
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
-
D.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
E.
commanderOfVictoriousSide
Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to another entity.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 1, 2026, 1:36 a.m.