Triple
T13551411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish SuperCup |
E323652
|
entity |
| Predicate | hasOfficialMatchBall |
P63333
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Polish SuperCup, hasOfficialMatchBall, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialMatchBall Context triple: [Polish SuperCup, hasOfficialMatchBall, yes]
-
A.
usesOfficialBallSupplier
Indicates that an entity makes use of a designated official supplier for the balls used in its activities or events.
-
B.
matchBall
chosen
Indicates that an entity is associated with or participates in a particular ball used in a match or game.
-
C.
formerOfficialGameBallSupplierFor
Indicates that an entity previously served as the official supplier of game balls for another entity (such as a league, team, or competition).
-
D.
firstWorldCupBallWith
Indicates that an entity was used as the official match ball in the first FIFA World Cup involving another specified entity (such as a team, match, or tournament edition).
-
E.
officialBallSport
Indicates that a sport is officially recognized as a ball sport, i.e., one whose play fundamentally involves the use of a ball.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:46 p.m.