Triple

T7219953
Position Surface form Disambiguated ID Type / Status
Subject Alexander family heirs E150231 entity
Predicate hasAncestor P369 FINISHED
Object John Alexander E28000 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: John Alexander | Statement: [Alexander family heirs, hasAncestor, John Alexander]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: John Alexander
Context triple: [Alexander family heirs, hasAncestor, John Alexander]
  • A. John Alexander chosen
    John Alexander was a prominent landowner in colonial Virginia whose family holdings encompassed the area that later became the city of Alexandria.
  • B. John Alexander
    John Alexander is an American actor and creature performer known for his work in practical effects and suit acting in fantasy and science fiction films.
  • C. John Alexander
    John Alexander was an American character actor best known for his comedic and eccentric roles in classic Hollywood films of the 1930s and 1940s.
  • D. Alexander Bruce
    Alexander Bruce was a medieval Scottish nobleman of the influential Bruce family, related to the line that produced King Robert the Bruce.
  • E. Alistair
    Alistair is a masculine given name of Scottish origin commonly used in English-speaking countries.
  • 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_69c687effb44819092b95d07d0368c9f completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e9b1a7908190bd215ffb84592e32 completed March 27, 2026, 8:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7d38423bc8190aaf4ee3940813d33 completed March 28, 2026, 1:11 p.m.
Created at: March 27, 2026, 2:53 p.m.