Triple

T28889991
Position Surface form Disambiguated ID Type / Status
Subject Great Gate E732668 entity
Predicate afterBreached P171010 FINISHED
Object repaired after the War of the Ring 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: repaired after the War of the Ring | Statement: [Great Gate, afterBreached, repaired after the War of the Ring]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: afterBreached
Context triple: [Great Gate, afterBreached, repaired after the War of the Ring]
  • A. breachedDuring
    Indicates that one entity violated, broke, or failed to uphold another entity (such as a rule, contract, or security measure) within a specified time period or event.
  • B. riskIfBreached
    Indicates that a breach of the referenced entity or condition would expose or create a potential risk or harm.
  • C. defensiveLineBreached
    Indicates that a defensive line or barrier has been successfully penetrated or overcome by an opposing force.
  • D. after
    Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
  • E. afterRepudiation
    Indicates that one event, state, or action occurs subsequent to and as a consequence of a prior repudiation (rejection or disavowal) of an obligation, agreement, or relationship.
  • 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_69f05b07bdec819080cadfe147aa1f25 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f6984bb55c8190862eb8796868d188 completed May 3, 2026, 12:35 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
PDg Predicate description generation batch_69f6978ec27c8190a488e1f9c2566d38 completed May 3, 2026, 12:32 a.m.
Created at: April 28, 2026, 7:54 a.m.