Triple

T12599344
Position Surface form Disambiguated ID Type / Status
Subject William Lambton E300814 entity
Predicate influenced P9 FINISHED
Object George Everest E97375 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: George Everest | Statement: [William Lambton, influenced, George Everest]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: George Everest
Context triple: [William Lambton, influenced, George Everest]
  • A. George Everest chosen
    George Everest was a 19th-century British surveyor and geographer who served as Surveyor General of India and lent his name to Mount Everest.
  • B. Everest
    Everest is a 2015 survival drama film that chronicles the harrowing true story of a deadly Mount Everest expedition.
  • C. Everest
    Everest is the codename for the high-performance CPU cores used in Apple’s A16 Bionic chip.
  • D. Mount Everest
    Mount Everest is the world's highest mountain above sea level, located in the Himalayas on the border between Nepal and the Tibet Autonomous Region of China.
  • E. Everes
    Everes is a figure in Greek mythology known primarily as the father of the blind prophet Tiresias.
  • 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_69d7bdea2ca881908f379526c13b1145 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d954d096d08190afa1f685bad68d35 completed April 10, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f684d8b8d081908f271e75e6472914 completed May 2, 2026, 11:12 p.m.
Created at: April 9, 2026, 5:09 p.m.