Triple
T17427427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. Charleroi S.C. |
E423774
|
entity |
| Predicate | hasRival |
P1375
|
FINISHED |
| Object | Standard Liège |
—
|
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: Standard Liège | Statement: [R. Charleroi S.C., hasRival, Standard Liège]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Standard Liège Context triple: [R. Charleroi S.C., hasRival, 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.
Liège-Guillemins
Liège-Guillemins is a major high-speed railway station in Liège, Belgium, renowned for its striking modern architecture designed by Santiago Calatrava.
-
C.
Leffe
Leffe is a historic Belgian abbey beer brand known for its rich, flavorful ales, now produced and marketed globally by AB InBev.
-
D.
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.
-
E.
Jupiler
Jupiler is a popular Belgian pilsner beer brand widely known for its strong association with football and major sports sponsorships.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fdc1348190985db52c8c74c394 |
completed | April 19, 2026, 3:16 a.m. |
Created at: April 10, 2026, 5:46 a.m.