Triple
T8411787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mylae |
E198640
|
entity |
| Predicate | combatantRoleOf |
P28183
|
FINISHED |
| Object | Roman Republic as attacker |
—
|
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: Roman Republic as attacker | Statement: [Battle of Mylae, combatantRoleOf, Roman Republic as attacker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantRoleOf Context triple: [Battle of Mylae, combatantRoleOf, Roman Republic as attacker]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
C.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
D.
combatantRoleOfUnitedKingdom
Indicates that the specified combatant role is one that was held by, or associated with, the United Kingdom in a particular conflict or military context.
-
E.
combatantsNationality
Indicates that the entities involved in a combat or conflict share or are associated with a specified nationality.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e0341c819080506e696131671e |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.