Triple

T18304294
Position Surface form Disambiguated ID Type / Status
Subject Onstwedde E438441 entity
Predicate roadAccessVia P9041 FINISHED
Object N374 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: N374 | Statement: [Onstwedde, roadAccessVia, N374]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: N374
Context triple: [Onstwedde, roadAccessVia, N374]
  • A. N374 chosen
    N374 is a regional road in the Netherlands that connects the town of Stadskanaal with other nearby localities in the province of Groningen.
  • B. N379
    N379 is a regional road in the Netherlands that serves as a key route connecting the village of Ter Apel with surrounding areas.
  • C. N367
    N367 is a regional road in the Netherlands that connects several towns in the province of Groningen, facilitating local and regional traffic.
  • D. N304
    N304 is a regional road in the Netherlands that connects the village of Harskamp with other nearby towns and routes.
  • E. N-370
    N-370 is a state highway in eastern Nebraska that serves as a major east–west arterial route connecting communities in the Omaha metropolitan area.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5018256508190b024980e3a4a3ae9 completed April 19, 2026, 4:23 p.m.
Created at: April 10, 2026, 10:35 a.m.