Triple

T21741207
Position Surface form Disambiguated ID Type / Status
Subject The Supper at Emmaus (Milan version) E536661 entity
Predicate cityOfMuseum P3049 FINISHED
Object Milan NE NERFINISHED

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: Milan | Statement: [The Supper at Emmaus (Milan version), cityOfMuseum, Milan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Milan
Context triple: [The Supper at Emmaus (Milan version), cityOfMuseum, Milan]
  • A. Milan
    Milan is a masculine given name of Slavic origin, commonly used in Central and Eastern Europe.
  • B. Milan
    Milan is a municipality located in Colombia’s Caquetá Department, within the Amazonian region of the country.
  • C. Milan chosen
    Milan is a major Italian metropolis renowned as a global center for fashion, design, finance, and culture.
  • D. Milan
    Milan is a village in northern Ohio best known as the birthplace of inventor Thomas Edison and for its historic canal-era architecture.
  • E. Milano
    Milano is a popular line of chocolate-filled sandwich cookies produced by Pepperidge Farm, a subsidiary of Campbell Soup Company.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46df5448190b4322127ffc4c690 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a7250d48190aa63f89db017ef70 completed April 28, 2026, 2:24 a.m.
Created at: April 16, 2026, 6:49 p.m.