Triple

T8306658
Position Surface form Disambiguated ID Type / Status
Subject Amstelstation E194478 entity
Predicate hasAbbreviation P43 FINISHED
Object Asd Amstel E4259 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: Asd Amstel | Statement: [Amstelstation, hasAbbreviation, Asd Amstel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asd Amstel
Context triple: [Amstelstation, hasAbbreviation, Asd Amstel]
  • A. Amsterdam Amstel chosen
    Amsterdam Amstel is a major railway and metro station in Amsterdam that serves as an important transport hub connecting regional and local lines.
  • B. 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.
  • C. Amstel brand
    Amstel brand is a Dutch beer brand best known for its lagers and international presence, produced under the ownership of Heineken.
  • D. Knooppunt Amstel
    Knooppunt Amstel is a major motorway interchange in Amsterdam that connects the A10 ring road with other key highways and routes into the city.
  • E. Ouder-Amstel
    Ouder-Amstel is a municipality in the province of North Holland in the Netherlands, located just southeast of Amsterdam.
  • 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_69ca82e613e88190bf8139669bbd0d53 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7f293db08190912e5e8bb7e940cf completed March 31, 2026, 8 a.m.
NED1 Entity disambiguation (via context triple) batch_69cdc6e4eb808190b138c52810f35040 completed April 2, 2026, 1:31 a.m.
Created at: March 30, 2026, 5:54 p.m.