Triple
T35996427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy War (Święta Wojna) Kraków derby |
E1040999
|
entity |
| Predicate | hasHomeStadiumForWisła |
P16388
|
FINISHED |
| Object | Stadion Miejski im. Henryka Reymana |
—
|
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: Stadion Miejski im. Henryka Reymana | Statement: [Holy War (Święta Wojna) Kraków derby, hasHomeStadiumForWisła, Stadion Miejski im. Henryka Reymana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeStadiumForWisła Context triple: [Holy War (Święta Wojna) Kraków derby, hasHomeStadiumForWisła, Stadion Miejski im. Henryka Reymana]
-
A.
isLocalStadiumFor
Indicates that a stadium serves as the primary home venue for a particular local team, club, or community.
-
B.
hasHomeStadiumContext
Indicates that an entity’s home stadium is specified or characterized within a particular contextual framework (such as time, competition, or role).
-
C.
hasTeamStadium
chosen
Indicates that a sports team is associated with or plays its home games at a particular stadium.
-
D.
leftStadium
Indicates that an entity has departed from or exited a stadium.
-
E.
neighbouringStadium
Indicates that one stadium is located adjacent to or very close to another stadium.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:07 p.m.