Triple

T22247003
Position Surface form Disambiguated ID Type / Status
Subject Joseph Addison Alexander E549870 entity
Predicate familyName P18 FINISHED
Object Alexander 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: Alexander | Statement: [Joseph Addison Alexander, familyName, Alexander]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alexander
Context triple: [Joseph Addison Alexander, familyName, Alexander]
  • A. Alexander
    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
    "Alexander" is an epic historical drama film directed by Oliver Stone that chronicles the life and conquests of Alexander the Great.
  • D. Alexander
    Alexander is another name for Paris, the Trojan prince in Greek mythology whose abduction of Helen sparked the Trojan War.
  • E. Alexander chosen
    Alexander is a common surname of Greek origin that has been borne by numerous notable figures across history and culture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e41d9408190bd770cf282e22753 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f13218d1f88190b64b7f301328fa98 completed April 28, 2026, 10:18 p.m.
Created at: April 16, 2026, 8:38 p.m.