Triple

T14274821
Position Surface form Disambiguated ID Type / Status
Subject Simon May E353887 entity
Predicate basedIn P40 FINISHED
Object London E1817 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: London | Statement: [Simon May, basedIn, London]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: London
Context triple: [Simon May, basedIn, London]
  • A. London
    London is a major Ethereum network upgrade that introduced significant changes to the protocol’s fee market and transaction pricing mechanisms.
  • B. London
    London is a major city in Kiribati, located on Kiritimati (Christmas Island) in the central Pacific Ocean.
  • C. London, England chosen
    London, England is the capital and largest city of the United Kingdom, renowned as a global center for finance, culture, and politics.
  • D. Allondon
    Allondon is a small river in western Switzerland and neighboring France, known for flowing through the Geneva region and its natural, relatively unspoiled surroundings.
  • E. York, England
    York, England is a historic walled city in northern England renowned for its medieval architecture, including York Minster, and its rich Roman and Viking heritage.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6582f5308190969f4cfd724d9139 completed April 14, 2026, 4:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd3d0e6abc819097c0c9bdc08387f6 completed May 8, 2026, 1:31 a.m.
Created at: April 10, 2026, 1:10 a.m.