Triple

T17142039
Position Surface form Disambiguated ID Type / Status
Subject Roy Nachum E415990 entity
Predicate hasExhibitedIn P25599 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: [Roy Nachum, hasExhibitedIn, London]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: London
Context triple: [Roy Nachum, hasExhibitedIn, 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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f2d5de10819090cbd65661b018d3 completed April 18, 2026, 9:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0141422d6c819086dc98988c0851d9 completed May 11, 2026, 2:38 a.m.
Created at: April 10, 2026, 5:36 a.m.