Triple
T29934277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Argentovaria |
E760312
|
entity |
| Predicate | AlamannicGroupInvolved |
P95521
|
FINISHED |
| Object | Lentienses |
—
|
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: Lentienses | Statement: [Battle of Argentovaria, AlamannicGroupInvolved, Lentienses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlamannicGroupInvolved Context triple: [Battle of Argentovaria, AlamannicGroupInvolved, Lentienses]
-
A.
GermanicForces
chosen
Indicates a relationship where certain forces or military units are identified as belonging to or associated with Germanic groups.
-
B.
alliedGroups
Indicates that two or more groups are formally cooperating or aligned in support of shared goals or interests.
-
C.
GermanicLeader
Indicates that an entity serves as a leader or ruling figure within a Germanic group, tribe, or people.
-
D.
CimbriTeutonesCommander
Indicates that a person served as a military commander of the Cimbri and Teutones.
-
E.
commanderOfVisigothicForces
Indicates that one entity serves as the military commander of the Visigothic forces in a given context or 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d346e4819089c1c7231d9df64e |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:19 p.m.