Triple
T16495683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łódź derby |
E400676
|
entity |
| Predicate | hasHomeStadiumForMatches |
P2696
|
FINISHED |
| Object | stadium of Widzew Łódź |
—
|
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: stadium of Widzew Łódź | Statement: [Łódź derby, hasHomeStadiumForMatches, stadium of Widzew Łódź]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeStadiumForMatches Context triple: [Łódź derby, hasHomeStadiumForMatches, stadium of Widzew Łódź]
-
A.
hasTeamStadium
Indicates that a sports team is associated with or plays its home games at a particular stadium.
-
B.
hasHostStadiumTeam
Indicates that a particular team is the primary host or home team for events held at a given stadium.
-
C.
hasHomeCityTeamStadium
Indicates that a sports team’s home city is associated with a specific stadium where the team primarily hosts its home games.
-
D.
homeStadiumOf
chosen
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
associatedStadiums
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e332c1c8190888a042d0192233a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.