Triple

T35655292
Position Surface form Disambiguated ID Type / Status
Subject Henrician castles E1030265 entity
Predicate replacedEarlierDefences P196190 FINISHED
Object medieval curtain-wall castles 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: medieval curtain-wall castles | Statement: [Henrician castles, replacedEarlierDefences, medieval curtain-wall castles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacedEarlierDefences
Context triple: [Henrician castles, replacedEarlierDefences, medieval curtain-wall castles]
  • A. introducedDefence
    Indicates that an entity has formally presented or initiated a defence, typically in response to an accusation, claim, or attack, within a given context or proceeding.
  • B. defenceUsed
    Indicates that a particular defensive measure, tactic, or argument was employed in response to a threat, attack, or accusation.
  • C. providesDefence
    Indicates that one entity offers protection or defensive support to another entity.
  • D. defenceHandledBy
    Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
  • E. removesDefence
    Indicates that one entity takes away, disables, or nullifies the protective capability or defense of another entity.
  • F. None of above. chosen

Provenance (4 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_69f76e0938088190a8f199631e97dec3 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fe12a899d4819080d48423f32eace9 completed May 8, 2026, 4:43 p.m.
PD Predicate disambiguation batch_69fe0d7f6aa08190a1d2dfc025d4e0dc completed May 8, 2026, 4:21 p.m.
PDg Predicate description generation batch_69fe12a769c08190bc445d302d2e8f98 completed May 8, 2026, 4:43 p.m.
Created at: May 3, 2026, 4:05 p.m.