Triple
T4653460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bouvines |
E102351
|
entity |
| Predicate | opponentCoalition |
P42770
|
FINISHED |
| Object | imperial and Anglo-Flemish coalition |
—
|
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: imperial and Anglo-Flemish coalition | Statement: [Battle of Bouvines, opponentCoalition, imperial and Anglo-Flemish coalition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentCoalition Context triple: [Battle of Bouvines, opponentCoalition, imperial and Anglo-Flemish coalition]
-
A.
opposingAlliance
chosen
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
B.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
-
C.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
D.
keyCoalition
Indicates a coalition relationship where an entity plays a central or decisive role within that coalition.
-
E.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd631623d881908a59dafa7702af54 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.