Triple

T16404079
Position Surface form Disambiguated ID Type / Status
Subject Nmnl E398378 entity
Predicate codeFor P3746 FINISHED
Object Nijmegen Lent E1045528 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: Nijmegen Lent | Statement: [Nmnl, codeFor, Nijmegen Lent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nijmegen Lent
Context triple: [Nmnl, codeFor, Nijmegen Lent]
  • A. Nijmegen Lent chosen
    Nijmegen Lent is a railway station in the Dutch city of Nijmegen that serves local and regional train services on the Arnhem–Nijmegen line.
  • B. Nijmegen Quarter
    Nijmegen Quarter was a historical administrative region centered around the city of Nijmegen within the medieval Duchy of Guelders in the Low Countries.
  • C. Utrecht Lunetten
    Utrecht Lunetten is a suburban railway station in the southeastern part of Utrecht in the Netherlands, serving the Lunetten residential district with regional train connections.
  • D. Utrecht Overvecht
    Utrecht Overvecht is a suburban railway station in the Overvecht district of Utrecht in the Netherlands, serving as a local commuter hub.
  • E. New Utrecht
    New Utrecht is a historic neighborhood in the southwestern part of Brooklyn, New York City, originally founded as a Dutch town in the 17th century.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d12dc08190a5b497692b667ed7 completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a003c6094e481909aa7402fd17fedae completed May 10, 2026, 8:05 a.m.
Created at: April 10, 2026, 5:09 a.m.