Triple

T7190824
Position Surface form Disambiguated ID Type / Status
Subject IJssel E167684 entity
Predicate tributary P415 FINISHED
Object Berkel E547487 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: Berkel | Statement: [IJssel, tributary, Berkel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Berkel
Context triple: [IJssel, tributary, Berkel]
  • A. Berkel chosen
    The Berkel is a river in the eastern Netherlands and western Germany that flows through the Achterhoek region before joining the IJssel.
  • B. Hanford
    Hanford is a village in Staffordshire, England, situated near the town of Trentham and forming part of the wider Stoke-on-Trent urban area.
  • C. Hanford
    Hanford is a small agricultural and commercial city in California’s San Joaquin Valley, known as a regional hub for farming, dairy production, and historic downtown architecture.
  • D. Livermore
    Livermore is a city in California’s Tri-Valley region known for its wine country, historic downtown, and proximity to major scientific research facilities.
  • E. Berkelland
    Berkelland is a municipality in the eastern Netherlands, located in the Achterhoek region of the province of Gelderland.
  • 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_69c6888b5248819090499a884ee3ec39 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e90087208190a65e49ae0e8a7cbf completed March 27, 2026, 8:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7b95c671c8190bf75b5807c6c320c completed March 28, 2026, 11:19 a.m.
Created at: March 27, 2026, 2:50 p.m.