Triple

T19531157
Position Surface form Disambiguated ID Type / Status
Subject A10 E488654 entity
Predicate hasJunction P1018 FINISHED
Object Knooppunt Amstel 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: Knooppunt Amstel | Statement: [A10, hasJunction, Knooppunt Amstel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Knooppunt Amstel
Context triple: [A10, hasJunction, Knooppunt Amstel]
  • A. Knooppunt Amstel chosen
    Knooppunt Amstel is a major motorway interchange in Amsterdam that connects the A10 ring road with other key highways and routes into the city.
  • B. Amsterdam Amstel
    Amsterdam Amstel is a major railway and metro station in Amsterdam that serves as an important transport hub connecting regional and local lines.
  • C. Amstel
    The Amstel is a river in the Netherlands that flows through Amsterdam and has given its name to the city and a well-known Dutch beer brand.
  • D. Amstel brand
    Amstel brand is a Dutch beer brand best known for its lagers and international presence, produced under the ownership of Heineken.
  • E. Brussels brewers’ corporation
    The Brussels brewers’ corporation is a historic guild of beer makers in Brussels that played a central role in regulating and promoting the city’s brewing trade.
  • 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_69d8e8db5b6c8190984b61f91981f575 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6363ec6cc8190b9e9ac0196b288f9 completed April 20, 2026, 2:20 p.m.
Created at: April 10, 2026, 1:41 p.m.