Triple
T3986877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camille d'Hostun, duc de Tallard |
E86893
|
entity |
| Predicate | resultOfBattleOfBlenheimForHim |
P19109
|
FINISHED |
| Object | defeat |
—
|
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: defeat | Statement: [Camille d'Hostun, duc de Tallard, resultOfBattleOfBlenheimForHim, defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBattleOfBlenheimForHim Context triple: [Camille d'Hostun, duc de Tallard, resultOfBattleOfBlenheimForHim, defeat]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
RoyalistArmyOutcome
Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
-
C.
monarchKilledInBattle
Indicates that a monarch died as a direct result of being killed during a battle.
-
D.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
-
E.
dateOfVictory
Indicates the specific calendar date on which a victory or winning outcome occurred.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.