Triple

T1815133
Position Surface form Disambiguated ID Type / Status
Subject Pont Alexandre III E40419 entity
Predicate crosses P416 FINISHED
Object Seine E6962 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: Seine | Statement: [Pont Alexandre III, crosses, Seine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seine
Context triple: [Pont Alexandre III, crosses, Seine]
  • A. Rhine
    The Rhine is one of Europe's most important rivers, historically serving as a vital trade route and cultural boundary from the Alps through Germany to the North Sea.
  • B. River Seine chosen
    The River Seine is a major waterway in northern France that flows through the heart of Paris and is central to the city's history, culture, and landscape.
  • C. Meuse
    Meuse is a department in northeastern France known for its rural landscapes and significant World War I battlefields, including Verdun.
  • D. Meuse
    The Meuse is a major European river flowing through France, Belgium, and the Netherlands, historically important for transport, trade, and the development of surrounding regions.
  • E. Rhens
    Rhens is a historic town on the Rhine River in western Germany, known for its medieval role as a meeting place of the prince-electors of the Holy Roman Empire.
  • 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_69a8864526c081908a3a4d74f689e2c5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa65f4628481909ca8e4c2302752ac completed March 6, 2026, 5:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69af8336f98c8190949c0145d2d31a8f completed March 10, 2026, 2:34 a.m.
Created at: March 4, 2026, 7:32 p.m.