Triple
T31874374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Argentoratum |
E813696
|
entity |
| Predicate | opponentTribe |
P88397
|
FINISHED |
| Object | Alemanni |
—
|
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: Alemanni | Statement: [Battle of Argentoratum, opponentTribe, Alemanni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentTribe Context triple: [Battle of Argentoratum, opponentTribe, Alemanni]
-
A.
enemyTribe
chosen
Indicates that one tribe is in an adversarial or hostile relationship with another tribe.
-
B.
combatantTribe
Indicates a tribal group that participates as a fighter or belligerent party in a conflict or battle.
-
C.
opponentGroup
Indicates that one group is in opposition or conflict with another group, typically as a rival, competitor, or adversary.
-
D.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
E.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 11:55 p.m.