Triple
T35996178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henryk Reyman Municipal Stadium |
E1040992
|
entity |
| Predicate | isNamedForClubLegendOf |
P24365
|
FINISHED |
| Object | Wisła Kraków |
—
|
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: Wisła Kraków | Statement: [Henryk Reyman Municipal Stadium, isNamedForClubLegendOf, Wisła Kraków]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedForClubLegendOf Context triple: [Henryk Reyman Municipal Stadium, isNamedForClubLegendOf, Wisła Kraków]
-
A.
isNamedFor
chosen
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
B.
clubLegendOf
Indicates that a person is widely regarded as a legendary or iconic figure for a particular club, typically due to exceptional contribution or long-term impact.
-
C.
isNamedForPersonFrom
Indicates that an entity is named after a person who originates from a specified place or region.
-
D.
legendaryNameFor
Indicates that one entity is known or referred to by the other entity as its legendary or mythic name.
-
E.
hasFanOrganizationNamedAfterIt
Indicates that an entity has a fan organization whose official name is derived from or explicitly references that 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.