Triple
T26030267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 AFF Championship |
E647411
|
entity |
| Predicate | qualifyingTeams |
P96366
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [2008 AFF Championship, qualifyingTeams, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifyingTeams Context triple: [2008 AFF Championship, qualifyingTeams, 10]
-
A.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
B.
qualifiedTeam
Indicates that a team has met the necessary criteria or achieved the required results to advance or be accepted into a particular stage, event, or competition.
-
C.
qualifiedTeamsCount
chosen
Indicates the number of teams that have successfully met the criteria to qualify for a given stage, event, or competition.
-
D.
numberOfParticipatingTeamsInQualifying
Indicates the total number of teams that take part in the qualifying stage of a competition or event.
-
E.
championQualifiedTeam
Indicates that a team has successfully qualified to participate in a championship competition.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 22, 2026, 9:06 a.m.