Triple

T17133740
Position Surface form Disambiguated ID Type / Status
Subject Siege of Rome (537–538) E415782 entity
Predicate primaryObjectiveOfDefender P56145 FINISHED
Object maintain Byzantine control of Rome 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: maintain Byzantine control of Rome | Statement: [Siege of Rome (537–538), primaryObjectiveOfDefender, maintain Byzantine control of Rome]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryObjectiveOfDefender
Context triple: [Siege of Rome (537–538), primaryObjectiveOfDefender, maintain Byzantine control of Rome]
  • A. objectiveOfDefenders chosen
    Indicates that a particular goal, task, or purpose is assigned to or pursued by the defenders in a given context.
  • B. protectionObjective
    Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
  • C. defender
    Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
  • D. defenderIn
    Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
  • E. objectiveOfAttackers
    Indicates the target or goal that attackers aim to reach or affect through their attack.
  • 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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f02cbb7881908aa69c3443d149d5 completed April 18, 2026, 8:57 p.m.
PD Predicate disambiguation batch_69e3830192ac819091344a9e5a36c8c9 completed April 18, 2026, 1:11 p.m.
Created at: April 10, 2026, 5:36 a.m.