Triple
T23035572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Asia Cup |
E573584
|
entity |
| Predicate | qualificationTournament |
P132582
|
FINISHED |
| Object | 2016 Asia Cup Qualifier |
—
|
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: 2016 Asia Cup Qualifier | Statement: [2016 Asia Cup, qualificationTournament, 2016 Asia Cup Qualifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualificationTournament Context triple: [2016 Asia Cup, qualificationTournament, 2016 Asia Cup Qualifier]
-
A.
qualifiedForTournament
Indicates that an entity meets the necessary criteria or requirements to participate in a particular tournament.
-
B.
qualificationHeld
Indicates that an entity possesses or has obtained a particular qualification or credential.
-
C.
qualificationStageIncluded
chosen
Indicates that a particular qualification stage is part of, or has been included within, a broader process, procedure, or evaluation sequence.
-
D.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
E.
playInTournamentIntroduced
Indicates that an entity participates as a player in a specific tournament that has been newly introduced or added.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1850df7fc81909ee522d99d96af0d |
completed | April 29, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.