Triple

T20499173
Position Surface form Disambiguated ID Type / Status
Subject river Eem E503254 entity
Predicate nearbyTown P3883 FINISHED
Object Eemnes NE NERFINISHED

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: Eemnes | Statement: [river Eem, nearbyTown, Eemnes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eemnes
Context triple: [river Eem, nearbyTown, Eemnes]
  • A. Eemnes chosen
    Eemnes is a small town and municipality in the central Netherlands known for its characteristic polder landscape and historic village centers.
  • B. Kvernes
    Kvernes is a village and historic parish area in Averøy Municipality in Møre og Romsdal county, Norway, known for its cultural heritage and scenic coastal landscape.
  • C. Sennevika
    Sennevika is a small settlement located on the island of Senja in northern Norway, known for its coastal Arctic landscape.
  • D. Smedvig
    Smedvig is a Norwegian family name most prominently associated with the Smedvig shipping and oil services business dynasty.
  • E. Emmen
    Emmen is a Swiss municipality located near the city of Lucerne, known for its industrial areas and residential communities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b1e52c8190894281cf7e3283ab completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69cbff210819089900e9a35911f48 completed April 20, 2026, 9:38 p.m.
Created at: April 16, 2026, 11:35 a.m.