Triple

T36887929
Position Surface form Disambiguated ID Type / Status
Subject Manius Curius Dentatus E911659 entity
Predicate roleInPyrrhicWar P108011 FINISHED
Object secured Roman victory over Pyrrhus 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: secured Roman victory over Pyrrhus in Italy | Statement: [Manius Curius Dentatus, roleInPyrrhicWar, secured Roman victory over Pyrrhus in Italy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInPyrrhicWar
Context triple: [Manius Curius Dentatus, roleInPyrrhicWar, secured Roman victory over Pyrrhus in Italy]
  • A. roleInWarOrConflict chosen
    Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
  • B. roleInTrojanWar
    Indicates the specific function, position, or part an entity played in the events of the Trojan War.
  • C. roleInTimeWar
    Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
  • D. roleInPunicWars
    Indicates the specific involvement, function, or position an entity had in the events or campaigns of the Punic Wars.
  • E. strategicRoleDuringWar
    Indicates that an entity served a particular strategic function or importance during a specific war or armed 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_69f76e8335908190b77e7e11d0e80820 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a01bb9c33cc8190a95ba124d97edf99 completed May 11, 2026, 11:21 a.m.
PD Predicate disambiguation batch_6a01bb6772148190a243d1141ad0a237 completed May 11, 2026, 11:20 a.m.
Created at: May 3, 2026, 4:13 p.m.