Triple
T22226551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosenborg Ballklub |
E549351
|
entity |
| Predicate | homeStadiumInstanceOf |
P21483
|
FINISHED |
| Object | football stadium |
—
|
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: football stadium | Statement: [Rosenborg Ballklub, homeStadiumInstanceOf, football stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStadiumInstanceOf Context triple: [Rosenborg Ballklub, homeStadiumInstanceOf, football stadium]
-
A.
homeStadiumType
chosen
Indicates the type or classification of a venue that serves as a team's primary home stadium.
-
B.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
C.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or organization.
-
D.
homeStadiumFeature
Indicates that a specified feature or characteristic is present in, or associated with, a team's home stadium.
-
E.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bee8de8819091ec5d14ea057f9e |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.