Triple

T14064414
Position Surface form Disambiguated ID Type / Status
Subject Andronikos II Palaiologos E338427 entity
Predicate givenName P17 FINISHED
Object Andronikos E907891 NE 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: Andronikos | Statement: [Andronikos II Palaiologos, givenName, Andronikos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Andronikos
Context triple: [Andronikos II Palaiologos, givenName, Andronikos]
  • A. Andronikos chosen
    Andronikos is a Greek male given name historically borne by several Byzantine emperors and nobles, most notably members of the Palaiologos dynasty.
  • B. Dionysodorus
    Dionysodorus is a sophist who appears as a debating character in Plato’s dialogue "Euthydemus," known for his eristic and paradoxical argumentation.
  • C. Demetrios
    Demetrios is a Greek given name historically borne by several notable Byzantine figures, including members of the Palaiologos dynasty.
  • D. Dorotheos
    Dorotheos is a Greek given name of religious origin, meaning "gift of God."
  • E. Antonidas
    Antonidas is a powerful human archmage and former leader of the Kirin Tor in the Warcraft universe, renowned for his wisdom and pivotal role in the events surrounding the fall of Lordaeron.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5689c7f48190a47ca94eaa8a9ef9 completed April 14, 2026, 3 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb6673de881909653c7691422b800 completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:21 p.m.