Triple
T9896022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Elchingen |
E182173
|
entity |
| Predicate | NapoleonRole |
P28183
|
FINISHED |
| Object | overall commander of French operations in the Ulm campaign |
—
|
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: overall commander of French operations in the Ulm campaign | Statement: [Battle of Elchingen, NapoleonRole, overall commander of French operations in the Ulm campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NapoleonRole Context triple: [Battle of Elchingen, NapoleonRole, overall commander of French operations in the Ulm campaign]
-
A.
relativeTypeToNapoleonBonaparte
Indicates the specific familial relationship that an entity has to Napoleon Bonaparte.
-
B.
battleSecuredForNapoleon
Indicates that a battle was won or decisively secured in favor of Napoleon.
-
C.
NapoleonTitleWhileThere
Indicates that a specified title or rank was held by Napoleon during his presence at a particular place or in a particular context.
-
D.
roleInGallicWars
Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
-
E.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4a9d2f4819086cfdd42b613cd8c |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.