Triple

T2123856
Position Surface form Disambiguated ID Type / Status
Subject Duisburg E43985 entity
Predicate hasTwinTown P919 FINISHED
Object Calais E30799 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: Calais | Statement: [Duisburg, hasTwinTown, Calais]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Calais
Context triple: [Duisburg, hasTwinTown, Calais]
  • A. Calais chosen
    Calais is a major French port city on the northern coast, serving as one of the primary crossing points between France and England.
  • B. Cherbourg
    Cherbourg is a major French port city on the Cotentin Peninsula, known for its strategic naval harbor and cross-Channel ferry connections.
  • C. Honfleur
    Honfleur is a historic port town in Normandy, northern France, renowned for its picturesque old harbor, timber-framed houses, and association with Impressionist painters.
  • D. Boulogne-sur-Mer
    Boulogne-sur-Mer is a coastal city and major fishing port in northern France, located on the English Channel in the Pas-de-Calais department.
  • E. Saint-Malo
    Saint-Malo is a historic walled port city in Brittany, northwestern France, known for its maritime heritage, privateering past, and dramatic coastal setting on the English Channel.
  • 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_69a88717cfe48190b7ecdd68c824848a completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abbb55cb2c8190aab8199da3335032 completed March 7, 2026, 5:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae519bfdb08190a7b715fbc5fd3f41 completed March 9, 2026, 4:50 a.m.
Created at: March 4, 2026, 7:44 p.m.