Triple

T7752052
Position Surface form Disambiguated ID Type / Status
Subject Aisne 1914 E175788 entity
Predicate namedAfter P63 FINISHED
Object Aisne River E368397 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: Aisne River | Statement: [Aisne 1914, namedAfter, Aisne River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aisne River
Context triple: [Aisne 1914, namedAfter, Aisne River]
  • A. Aisne
    Aisne is a department in northern France known for its historic towns, World War I battlefields, and rural landscapes.
  • B. Aisne chosen
    Aisne is a river in northeastern France that flows through the Champagne and Picardy regions before joining the Oise River.
  • C. Aube River
    The Aube River is a major waterway in northeastern France that flows through the Champagne region before joining the Seine.
  • D. Oise River
    The Oise River is a major waterway in northern France and southern Belgium that flows into the Seine and serves as an important route for inland navigation and commerce.
  • E. Marne
    The Marne is a major river in northeastern France that flows through the Île-de-France region before joining the Seine near Paris.
  • 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_69c6996180088190832e38e8d83ff54a completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c703b382588190ad8dc7138987829a completed March 27, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69d09b0002948190bb9d47cd0c766003 completed April 4, 2026, 5 a.m.
Created at: March 27, 2026, 4:08 p.m.