Triple
T27702524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC U-16 Women's Championship |
E698462
|
entity |
| Predicate | worldCupQualifierSlotFor |
P24783
|
FINISHED |
| Object | Asian teams |
—
|
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: Asian teams | Statement: [AFC U-16 Women's Championship, worldCupQualifierSlotFor, Asian teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldCupQualifierSlotFor Context triple: [AFC U-16 Women's Championship, worldCupQualifierSlotFor, Asian teams]
-
A.
qualifyingSlotsForWorldCup
chosen
Indicates the number or allocation of qualification spots available for the World Cup.
-
B.
confederationCupQualifier
Indicates that an entity has qualified for participation in a Confederations Cup tournament.
-
C.
usedAsWorldCupQualifier
Indicates that a match, tournament, or event served as a qualifying competition for participation in the FIFA World Cup.
-
D.
fifaWorldCupQualifyingParticipation
Indicates that an entity took part in the qualification stage for a FIFA World Cup tournament.
-
E.
worldCupZone
Indicates a relationship where a location, team, or match is associated with a specific geographic or organizational zone used for World Cup qualification or grouping.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 2:58 p.m.