Triple
T17992161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADIB Cup |
E430398
|
entity |
| Predicate | isCupCompetition |
P8324
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ADIB Cup, isCupCompetition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCupCompetition Context triple: [ADIB Cup, isCupCompetition, true]
-
A.
isPremierCupCompetitionOf
Indicates that one competition is the top-tier or most prestigious cup tournament associated with a particular sport, league, or organization.
-
B.
isDomesticCompetitionForAssociation
Indicates that a competition is a national or internal event organized under the authority of a specific sports association or governing body.
-
C.
leagueOrCup
Indicates that one entity is a league or cup competition in which the other entity participates or is associated.
-
D.
isTeamCompetition
Indicates that the competition involves participants organized into teams competing against each other rather than as individuals.
-
E.
cupCompetition
chosen
Indicates a competitive event or tournament, typically in a knockout or cup format, held between teams or individuals.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29fd7648190b7f09ea60c7b96a8 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.