Triple
T8046354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molde FK |
E187563
|
entity |
| Predicate | homeStadium |
P890
|
FINISHED |
| Object | Aker Stadion |
E370155
|
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: Aker Stadion | Statement: [Molde FK, homeStadium, Aker Stadion]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aker Stadion Context triple: [Molde FK, homeStadium, Aker Stadion]
-
A.
Aker Stadion
chosen
Aker Stadion is a football stadium in Molde, Norway, best known as the home ground of the Norwegian club Molde FK.
-
B.
Vålerenga Stadion
Vålerenga Stadion is a football stadium in Oslo, Norway, serving as the home ground of the Vålerenga Fotball club.
-
C.
Bryne Stadion
Bryne Stadion is a football stadium in Bryne, Norway, primarily known as the home ground of the Norwegian club Bryne FK.
-
D.
Sarpsborg Stadion
Sarpsborg Stadion is a football stadium in Sarpsborg, Norway, primarily used as the home ground of the club Sarpsborg 08 FF.
-
E.
Gjøvik Stadium
Gjøvik Stadium is a sports arena in Gjøvik, Norway, primarily used for football and athletics events.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4d9ddc8190a7dcf85ed47ee6c3 |
completed | March 31, 2026, 3:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc93c407cc81908029bfdd5a0393f1 |
completed | April 1, 2026, 3:40 a.m. |
Created at: March 30, 2026, 5:24 p.m.