Triple

T884677
Position Surface form Disambiguated ID Type / Status
Subject Alexander I of Russia E19103 entity
Predicate givenName P17 FINISHED
Object Alexander E5923 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: Alexander | Statement: [Alexander I of Russia, givenName, Alexander]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alexander
Context triple: [Alexander I of Russia, givenName, Alexander]
  • A. Alexander chosen
    Alexander is a common male given name of Greek origin, meaning "defender of men."
  • B. Alexander
    Alexander was one of the sons of Herod the Great, a Judean prince whose execution reflected the intense dynastic and political turmoil of Herod’s reign.
  • C. Alexander the Great
    Alexander the Great was a 4th-century BCE king of Macedon who created one of the largest empires in ancient history and spread Greek culture across the Near East.
  • D. Philip II of Macedon
    Philip II of Macedon was the 4th-century BCE king who transformed Macedonia into a dominant military power and laid the foundations for his son Alexander the Great’s vast empire.
  • E. Alexander the Fierce
    Alexander the Fierce is the epithet of Alexander I of Scotland, a 12th-century king noted for his vigorous rule and military assertiveness.
  • 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_69a4939c32488190a7ccd41cf0abb22b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ace5e15c81908cc2e648c9cd52f2 completed March 1, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69a9339ba2e48190872fd771386ba321 completed March 5, 2026, 7:41 a.m.
Created at: March 1, 2026, 7:39 p.m.