Triple

T33047302
Position Surface form Disambiguated ID Type / Status
Subject Ottoman capture of Nicomedia E845629 entity
Predicate impactOnByzantines P182432 FINISHED
Object loss of a key fortified city in Asia Minor 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: loss of a key fortified city in Asia Minor | Statement: [Ottoman capture of Nicomedia, impactOnByzantines, loss of a key fortified city in Asia Minor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: impactOnByzantines
Context triple: [Ottoman capture of Nicomedia, impactOnByzantines, loss of a key fortified city in Asia Minor]
  • A. impactOnConstantinople
    Indicates a relationship where one entity has an effect, influence, or consequence specifically on the city of Constantinople.
  • B. allyOfByzantines
    Indicates a relationship where an entity served as an ally or cooperative partner of the Byzantine Empire.
  • C. aimOfByzantines
    Indicates the goal or objective pursued by the Byzantines in a given context.
  • D. statusInByzantineEmpire
    Indicates the role, rank, or condition an entity held within the political or social structure of the Byzantine Empire.
  • E. opponentOfByzantines
    Indicates a relationship where an entity is an adversary or enemy of the Byzantines in a conflict or rivalry.
  • 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_69f3495242e48190996a2cb2beab5455 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f78d7211a48190bfb59c406f0bf12f completed May 3, 2026, 6:01 p.m.
PD Predicate disambiguation batch_69f78b8cb3a881909ebaac1b503988c2 completed May 3, 2026, 5:53 p.m.
PDg Predicate description generation batch_69f78c6014e08190864785a4fe3e8e73 completed May 3, 2026, 5:56 p.m.
Created at: May 1, 2026, 1:24 a.m.