Triple

T12350883
Position Surface form Disambiguated ID Type / Status
Subject RFC Liège E294480 entity
Predicate hasRivalryWith P893 FINISHED
Object Standard Liège E552945 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: Standard Liège | Statement: [RFC Liège, hasRivalryWith, Standard Liège]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Standard Liège
Context triple: [RFC Liège, hasRivalryWith, Standard Liège]
  • A. Standard Liège chosen
    Standard Liège is a prominent Belgian professional football club based in Liège, known for its rich history and multiple domestic league titles.
  • B. Leffe
    Leffe is a historic Belgian abbey beer brand known for its rich, flavorful ales, now produced and marketed globally by AB InBev.
  • C. BE333 Liège
    BE333 Liège is a NUTS 3 statistical region in Belgium that includes the city of Seraing and forms part of the broader Liège area in Wallonia.
  • D. Jupiler
    Jupiler is a popular Belgian pilsner beer brand widely known for its strong association with football and major sports sponsorships.
  • E. Brabantine gros
    The Brabantine gros was a medieval silver coin issued in the Duchy of Brabant, used widely in regional trade alongside larger gold denominations.
  • 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_69d6ab6ccbec8190b09e2d357aa80064 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f7cbff08190849cd2aec4ce3243 completed April 10, 2026, 6:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6346faa0481909e2f8463bff88c52 completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:53 p.m.