Triple
T27902386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar under-20 national football team |
E705670
|
entity |
| Predicate | bestAFCU20AsianCupResultYear |
P162963
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Qatar under-20 national football team, bestAFCU20AsianCupResultYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestAFCU20AsianCupResultYear Context triple: [Qatar under-20 national football team, bestAFCU20AsianCupResultYear, 2014]
-
A.
bestResultAFCAsianCup
Indicates the most successful performance or highest achievement an entity has attained in the AFC Asian Cup competition.
-
B.
bestResultInAFCU20AsianCup
chosen
Indicates the best performance or highest achievement a team has attained in the AFC U-20 Asian Cup tournament.
-
C.
afconTitleYear
Indicates the specific year in which a given Africa Cup of Nations (AFCON) title was won.
-
D.
afcU23AsianCupBestResultYear
Indicates the year in which an entity achieved its best performance in the AFC U-23 Asian Cup tournament.
-
E.
afconRunnerUpYear
Indicates the year in which a given team or country finished as runner-up in the Africa Cup of Nations (AFCON) tournament.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:43 p.m.