Triple

T28688006
Position Surface form Disambiguated ID Type / Status
Subject Lucius Antonius E729189 entity
Predicate roleInPerusineWar P108011 FINISHED
Object leader of senatorial and Antonian forces in Italy 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: leader of senatorial and Antonian forces in Italy | Statement: [Lucius Antonius, roleInPerusineWar, leader of senatorial and Antonian forces in Italy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInPerusineWar
Context triple: [Lucius Antonius, roleInPerusineWar, leader of senatorial and Antonian forces in Italy]
  • A. roleInWarOrConflict chosen
    Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
  • B. strategicRoleDuringWar
    Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
  • C. sideInFinnishCivilWar
    Indicates the faction or side that an entity aligned with or belonged to during the Finnish Civil War.
  • D. roleInTimeWar
    Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
  • E. worldWarIIRole
    Indicates the specific role, position, or function an entity had in relation to World War II.
  • 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_69f043e60b6c8190ac2cd042e77fe6e9 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69fe7bfc94bc81909eeec946e8c1c450 completed May 9, 2026, 12:12 a.m.
PD Predicate disambiguation batch_69fe7b74a1188190886f128e07f712da completed May 9, 2026, 12:10 a.m.
Created at: April 28, 2026, 5:34 a.m.