Triple

T10970960
Position Surface form Disambiguated ID Type / Status
Subject Bertrada of Laon E259230 entity
Predicate placeOfOrigin P3743 FINISHED
Object Laon E265383 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: Laon | Statement: [Bertrada of Laon, placeOfOrigin, Laon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laon
Context triple: [Bertrada of Laon, placeOfOrigin, Laon]
  • A. Laon chosen
    Laon is a historic hilltop city in northern France known for its well-preserved medieval architecture and impressive Gothic cathedral.
  • B. Troyes
    Troyes is a historic city in northeastern France, known for its well-preserved medieval old town, half-timbered houses, and Gothic churches.
  • C. Reims
    Reims is a historic city in northeastern France known for its Gothic cathedral, role in French coronations, and significance during both World Wars.
  • D. Draveil
    Draveil is a suburban commune in the southern Île-de-France region of France, located near Paris along the Seine River.
  • E. Creil
    Creil is a commuter town in northern France’s Oise department, known as a regional rail hub connecting Paris with Picardy via major train and RER lines.
  • 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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7719a27488190b0b723cd0aba40bd completed April 9, 2026, 9:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69f63ed654848190b53e8b64d81eb143 completed May 2, 2026, 6:13 p.m.
Created at: April 8, 2026, 9:24 p.m.