Triple

T37651295
Position Surface form Disambiguated ID Type / Status
Subject First Siege of Athlone (1690) E937179 entity
Predicate comparedWithLaterEvent P191995 FINISHED
Object Second Siege of Athlone (1691) NE NERFINISHED

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: Second Siege of Athlone (1691) | Statement: [First Siege of Athlone (1690), comparedWithLaterEvent, Second Siege of Athlone (1691)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: comparedWithLaterEvent
Context triple: [First Siege of Athlone (1690), comparedWithLaterEvent, Second Siege of Athlone (1691)]
  • A. coversEventsAfter
    Indicates that one event or time interval extends to include all events occurring after a specified reference event or time.
  • B. comparedToSuccessor chosen
    Indicates that an entity is being evaluated or measured in relation to the entity that immediately follows it in a sequence or ordered set.
  • C. notEarlierThan
    Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
  • D. arisesAfter
    Indicates that one event, state, or condition comes into existence or begins only after another specified event, state, or condition has occurred.
  • E. createdAfterEvent
    Indicates that the creation of one entity occurred after a specified event in time.
  • 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_69f76ed4fe908190b8061c5c135e0971 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fdbc5ef46c8190bbcfb9798f4615b7 completed May 8, 2026, 10:35 a.m.
PD Predicate disambiguation batch_69fdbb270338819082ce3f73903e884f completed May 8, 2026, 10:29 a.m.
Created at: May 3, 2026, 4:18 p.m.