Triple

T13704231
Position Surface form Disambiguated ID Type / Status
Subject Eemnes E328597 entity
Predicate locatedOn P40 FINISHED
Object river Eem E503254 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: river Eem | Statement: [Eemnes, locatedOn, river Eem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: river Eem
Context triple: [Eemnes, locatedOn, river Eem]
  • A. river Eem chosen
    The river Eem is a short Dutch river in the province of Utrecht that flows through towns such as Amersfoort and Baarn before emptying into the Eemmeer.
  • B. river IJssel
    The river IJssel is a major distributary of the Rhine in the eastern Netherlands, flowing north through the provinces of Gelderland and Overijssel into the IJsselmeer.
  • C. Eems
    Eems is the Dutch name for the Ems River, a major waterway in northwestern Europe that flows through Germany and the Netherlands into the North Sea.
  • D. Drentsche Aa
    Drentsche Aa is a small, meandering river in the Dutch province of Drenthe, renowned for its well-preserved natural landscape and surrounding national park.
  • E. River Nederrijn
    The River Nederrijn is a major distributary branch of the Rhine in the Netherlands, flowing through the central part of the country and playing a key role in its inland waterway network.
  • 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_69d8076ff62081908a7bd79889edd7a0 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dcad162158819089280ee1e6b5c2cf completed April 13, 2026, 8:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69fbc315ff848190a6c8cbd5b90db7fc completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 9:54 p.m.