Triple
T29796877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Noreia |
E756576
|
entity |
| Predicate | tribalForces |
P88504
|
FINISHED |
| Object | migrating Cimbri and Teutones |
—
|
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: migrating Cimbri and Teutones | Statement: [Battle of Noreia, tribalForces, migrating Cimbri and Teutones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalForces Context triple: [Battle of Noreia, tribalForces, migrating Cimbri and Teutones]
-
A.
combatantTribe
chosen
Indicates a tribal group that participates as a fighter or belligerent party in a conflict or battle.
-
B.
enemyTribe
Indicates that one tribe is in an adversarial or hostile relationship with another tribe.
-
C.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
E.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e7548c81909acffee32ca126f9 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:15 p.m.