Triple
T7709823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Abensberg |
E174718
|
entity |
| Predicate | FrenchAllies |
P16682
|
FINISHED |
| Object | Bavarian troops |
—
|
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: Bavarian troops | Statement: [Battle of Abensberg, FrenchAllies, Bavarian troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchAllies Context triple: [Battle of Abensberg, FrenchAllies, Bavarian troops]
-
A.
alliedForces
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
B.
majorAllies
Indicates that the entities are principal or primary allies, signifying a strong, significant, and mutually supportive alliance between them.
-
C.
alliedCountries
Indicates that two countries are formally cooperating as allies, typically through mutual support agreements or shared strategic interests.
-
D.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
-
E.
alliesInWar
chosen
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.