Triple
T21639777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vålerenga kultur- og idrettspark |
E534059
|
entity |
| Predicate | homeVenueForLeague |
P36103
|
FINISHED |
| Object | Eliteserien (Vålerenga home matches) |
—
|
LITERAL 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: Eliteserien (Vålerenga home matches) | Statement: [Vålerenga kultur- og idrettspark, homeVenueForLeague, Eliteserien (Vålerenga home matches)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueForLeague Context triple: [Vålerenga kultur- og idrettspark, homeVenueForLeague, Eliteserien (Vålerenga home matches)]
-
A.
homeVenueTeam1City
Indicates that a specific city serves as the home venue location for the first team in a given context or event.
-
B.
homeVenueTeam2City
Indicates that a second home venue team is based in or associated with a particular city.
-
C.
gameVenue
Indicates the location or facility where a game or match is held.
-
D.
leagueVenueFor
chosen
Indicates that a venue is used as the hosting location for events or competitions of a particular league.
-
E.
homeVenueOfOwnedTeam
Indicates that a venue serves as the primary home location for a sports team that is owned by a specified owner.
- F. None of above.
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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5390ba7481908f58230779e5b7bb |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.