Triple

T15520427
Position Surface form Disambiguated ID Type / Status
Subject Thomas Bladen Alexander E368947 entity
Predicate family name P18 FINISHED
Object Alexander E596604 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: [Thomas Bladen Alexander, family name, Alexander]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alexander
Context triple: [Thomas Bladen Alexander, family name, Alexander]
  • A. Alexander
    Alexander is another name for Paris, the Trojan prince in Greek mythology whose abduction of Helen sparked the Trojan War.
  • B. Alexander
    Alexander is a common male given name of Greek origin, meaning "defender of men."
  • C. 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.
  • D. Alexander
    "Alexander" is an epic historical drama film directed by Oliver Stone that chronicles the life and conquests of Alexander the Great.
  • 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 (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_69d85a1794cc8190b0b428716296e63e completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0403543188190abac49d2b9decb89 completed April 16, 2026, 1:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d54ea5c8190b3b220ad10ba8f40 completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 4:04 a.m.