Triple
T11231774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K.S.C. Lokeren Oost-Vlaanderen |
E265838
|
entity |
| Predicate | homeStadium |
P890
|
FINISHED |
| Object |
Daknamstadion
Daknamstadion is a football stadium in Lokeren, Belgium, best known as the long-time home ground of K.S.C. Lokeren Oost-Vlaanderen.
|
E912954
|
NE FINISHED |
How this triple was built (4 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: Daknamstadion | Statement: [K.S.C. Lokeren Oost-Vlaanderen, homeStadium, Daknamstadion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daknamstadion Context triple: [K.S.C. Lokeren Oost-Vlaanderen, homeStadium, Daknamstadion]
-
A.
Nadderud Stadion
Nadderud Stadion is a football stadium in Bærum, Norway, best known as the long-time home ground of Norwegian club Stabæk Fotball.
-
B.
Alverbergstadion
Alverbergstadion is a football stadium located in Hasselt, Belgium, serving as a home ground for local football clubs and sporting events.
-
C.
Viking Stadion
Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
-
D.
Lerkendal Stadion
Lerkendal Stadion is a major football stadium in Trondheim, Norway, best known as the home ground of top Norwegian club Rosenborg BK.
-
E.
Aspmyra Stadion
Aspmyra Stadion is a football stadium in Bodø, Norway, best known as the home ground of FK Bodø/Glimt.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Daknamstadion Triple: [K.S.C. Lokeren Oost-Vlaanderen, homeStadium, Daknamstadion]
Generated description
Daknamstadion is a football stadium in Lokeren, Belgium, best known as the long-time home ground of K.S.C. Lokeren Oost-Vlaanderen.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Daknamstadion Target entity description: Daknamstadion is a football stadium in Lokeren, Belgium, best known as the long-time home ground of K.S.C. Lokeren Oost-Vlaanderen.
-
A.
Nadderud Stadion
Nadderud Stadion is a football stadium in Bærum, Norway, best known as the long-time home ground of Norwegian club Stabæk Fotball.
-
B.
Alverbergstadion
Alverbergstadion is a football stadium located in Hasselt, Belgium, serving as a home ground for local football clubs and sporting events.
-
C.
Viking Stadion
Viking Stadion is a football stadium in Stavanger, Norway, primarily serving as the home ground of Viking FK.
-
D.
Lerkendal Stadion
Lerkendal Stadion is a major football stadium in Trondheim, Norway, best known as the home ground of top Norwegian club Rosenborg BK.
-
E.
Aspmyra Stadion
Aspmyra Stadion is a football stadium in Bodø, Norway, best known as the home ground of FK Bodø/Glimt.
- F. None of above. chosen
Provenance (5 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9026e1c81909456ac946bbba972 |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4ad49b5cc8190b99cb2cd8de72109 |
completed | April 19, 2026, 10:24 a.m. |
| NEDg | Description generation | batch_69e4b12dd658819085c25d3edac2d66c |
completed | April 19, 2026, 10:40 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69e4b3d23b18819096f3a11aecc732bd |
completed | April 19, 2026, 10:52 a.m. |
Created at: April 8, 2026, 9:30 p.m.