Triple

T7657522
Position Surface form Disambiguated ID Type / Status
Subject Siege of Constantine (1836) E173422 entity
Predicate defendedWith P6876 FINISHED
Object fortified walls of Constantine 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: fortified walls of Constantine | Statement: [Siege of Constantine (1836), defendedWith, fortified walls of Constantine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defendedWith
Context triple: [Siege of Constantine (1836), defendedWith, fortified walls of Constantine]
  • A. defendedAs
    Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
  • B. defends chosen
    Indicates that one entity protects or supports another entity against attack, criticism, or harm.
  • C. defenderIn
    Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
  • D. defenceHandledBy
    Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
  • E. canBeDefendedIn
    Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
  • 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_69c69955517c819085bc715b96d304d2 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7061cbc3c8190a917dd7e71214182 completed March 27, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69c7015dd8fc8190bc5f52a12bd46209 completed March 27, 2026, 10:14 p.m.
Created at: March 27, 2026, 3:59 p.m.