Triple
T7620970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Antwerp F.C. |
E172488
|
entity |
| Predicate | usesStadiumForHomeMatches |
P47009
|
FINISHED |
| Object | Bosuilstadion |
E677277
|
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: Bosuilstadion | Statement: [Royal Antwerp F.C., usesStadiumForHomeMatches, Bosuilstadion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bosuilstadion Context triple: [Royal Antwerp F.C., usesStadiumForHomeMatches, Bosuilstadion]
-
A.
Bosuilstadion
chosen
Bosuilstadion is a historic football stadium in Antwerp, Belgium, best known as the long-time home ground of Royal Antwerp F.C.
-
B.
Alfheim Stadion
Alfheim Stadion is a football stadium in Tromsø, Norway, best known as the home ground of the Norwegian club Tromsø IL.
-
C.
Soevereinstadion
Soevereinstadion is a football stadium in Lommel, Belgium, primarily used for hosting the home matches of Lommel SK.
-
D.
Alverbergstadion
Alverbergstadion is a football stadium located in Hasselt, Belgium, serving as a home ground for local football clubs and sporting events.
-
E.
Viking Stadion
Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa62870c8190b17f44eb7a3ff2ad |
completed | March 27, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8709b93c881909dd4c8a7669279db |
completed | March 29, 2026, 12:21 a.m. |
Created at: March 27, 2026, 3:55 p.m.