Triple
T8097127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian Super Cup |
E189012
|
entity |
| Predicate | officialBallSport |
P80453
|
FINISHED |
| Object | association football |
—
|
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: association football | Statement: [Iranian Super Cup, officialBallSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialBallSport Context triple: [Iranian Super Cup, officialBallSport, association football]
-
A.
primarySport
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
-
B.
primarySports
Indicates that a particular sport is the main or most important sport associated with an entity (such as a person, team, or organization).
-
C.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
D.
favoriteSport
Indicates that one entity has a particular sport that it prefers above all others.
-
E.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
- F. None of above. chosen
Provenance (4 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb429319048190b612c8060a9a24d2 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:30 p.m.