Triple

T8967995
Position Surface form Disambiguated ID Type / Status
Subject Aleksandr E214186 entity
Predicate etymologicallyRelatedTo P5801 FINISHED
Object Alexandros E213222 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: Alexandros | Statement: [Aleksandr, etymologicallyRelatedTo, Alexandros]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alexandros
Context triple: [Aleksandr, etymologicallyRelatedTo, Alexandros]
  • A. Alexandros chosen
    Alexandros is a Greek given name, most famously borne by Alexander the Great, and is the Hellenic form of the name Alejandro/Alexander.
  • B. Alexander of Epirus
    Alexander of Epirus was a 4th-century BC Molossian king and uncle of Alexander the Great, known for his campaigns in southern Italy against various Italic peoples.
  • C. Demetrios
    Demetrios is a Greek given name historically borne by several notable Byzantine figures, including members of the Palaiologos dynasty.
  • D. Pleistarchus
    Pleistarchus was a 5th-century BC Eurypontid king of Sparta and son of the famous Spartan leader Pausanias.
  • E. Heracles of Macedon
    Heracles of Macedon was the illegitimate son of Alexander the Great who became a short-lived claimant to the Macedonian throne during the turbulent Successor period.
  • 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_69ca839dbf608190a2f5990477115d29 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6764aca48190a5e472d1b6841886 completed April 1, 2026, 12:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0174564188190a99e2d46a6563b69 completed April 3, 2026, 7:38 p.m.
Created at: March 30, 2026, 7:01 p.m.