Triple

T6143285
Position Surface form Disambiguated ID Type / Status
Subject Amstel E137013 entity
Predicate hasVariant P455 FINISHED
Object Amstel Lager E137013 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: Amstel Lager | Statement: [Amstel, hasVariant, Amstel Lager]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amstel Lager
Context triple: [Amstel, hasVariant, Amstel Lager]
  • A. 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.
  • 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. Heineken lager beer
    Heineken lager beer is a globally recognized pale lager known for its distinctive green bottle, red star logo, and crisp, mildly bitter taste.
  • D. Amstel brand chosen
    Amstel brand is a Dutch beer brand best known for its lagers and international presence, produced under the ownership of Heineken.
  • E. Grolsch
    Grolsch is a Dutch brewery best known for its distinctive swing-top bottled beers and long-standing presence in the international beer market.
  • 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_69c008a2c6308190a56519b22d55d083 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05cb50cb0819081ac64becf7aaf55 completed March 22, 2026, 9:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c135f88db881908b8a5d9c35bf0fbb completed March 23, 2026, 12:45 p.m.
Created at: March 22, 2026, 4:16 p.m.