Triple

T3949620
Position Surface form Disambiguated ID Type / Status
Subject Eve Myles E84831 entity
Predicate familyName P18 FINISHED
Object Myles E71664 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: Myles | Statement: [Eve Myles, familyName, Myles]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Myles
Context triple: [Eve Myles, familyName, Myles]
  • A. Myles chosen
    Myles is a masculine given name of English origin, historically associated with figures such as Mayflower military leader Myles Standish.
  • B. Aidan
    Aidan is a masculine given name of Irish origin that has become popular in many English-speaking countries.
  • C. Gavin
    Gavin is a masculine given name of Celtic origin, commonly used in English-speaking countries.
  • D. Romiley
    Romiley is a suburban village and residential area within the Metropolitan Borough of Stockport in Greater Manchester, England.
  • E. Reilly
    Reilly is a surname most notably associated with William K. Reilly, an American environmentalist and former administrator of the U.S. Environmental Protection Agency.
  • 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_69aed934fbfc8190847068e4546de963 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef91227a8819097c3a5a206792382 completed March 9, 2026, 4:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69b53ff967a88190b0100dbedb580e4d completed March 14, 2026, 11:01 a.m.
Created at: March 9, 2026, 3:30 p.m.