Triple

T14278421
Position Surface form Disambiguated ID Type / Status
Subject Battle of Lincoln (1141) E353976 entity
Predicate chronologyWithinTheAnarchy P26528 FINISHED
Object occurs roughly mid-way through the civil war (1135–1154) 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: occurs roughly mid-way through the civil war (1135–1154) | Statement: [Battle of Lincoln (1141), chronologyWithinTheAnarchy, occurs roughly mid-way through the civil war (1135–1154)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: chronologyWithinTheAnarchy
Context triple: [Battle of Lincoln (1141), chronologyWithinTheAnarchy, occurs roughly mid-way through the civil war (1135–1154)]
  • A. chronologyWithinConflict chosen
    Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
  • B. chronologyWithinReconquista
    Indicates that one event or period occurs temporally within the historical span of the Reconquista.
  • C. chronologyWithinRevolution
    Indicates that one event or time period occurs within the temporal span of a specified revolution.
  • D. chronologyOf
    Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
  • E. chronologyNote
    Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6585270c8190a717127b2f5dab3b completed April 14, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69de2a88446481909cd526da97a3b70f completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:10 a.m.