Triple
T33427869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silesian Stadium |
E856037
|
entity |
| Predicate | wasMainStadiumFor |
P2439
|
FINISHED |
| Object | Poland national football team |
—
|
NE NERFINISHED |
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: Poland national football team | Statement: [Silesian Stadium, wasMainStadiumFor, Poland national football team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMainStadiumFor Context triple: [Silesian Stadium, wasMainStadiumFor, Poland national football team]
-
A.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
B.
mainStadium
chosen
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
C.
usedAsOlympicStadiumFor
Indicates that a venue served as the official stadium for hosting events of a particular edition of the Olympic Games.
-
D.
playedAtStadium
Indicates that an event or game took place at, or was hosted in, a specific stadium.
-
E.
locatedInStadiumOf
Indicates that something is situated within the stadium that belongs to or is used by a particular entity.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.