Triple
T27688192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC competitions |
E698087
|
entity |
| Predicate | futsalTournament |
P65874
|
FINISHED |
| Object | AFC Women's Futsal Championship |
—
|
NE NERFINISHED |
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: AFC Women's Futsal Championship | Statement: [AFC competitions, futsalTournament, AFC Women's Futsal Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futsalTournament Context triple: [AFC competitions, futsalTournament, AFC Women's Futsal Championship]
-
A.
futsalCompetition
chosen
Indicates a competitive event or tournament in the sport of futsal involving participating teams or players.
-
B.
FIFATournament
Indicates a relationship where an entity is recognized as a tournament organized, sanctioned, or officially associated with FIFA.
-
C.
beachSoccerTournament
Indicates that a beach soccer tournament event is taking place or is associated with the specified entities.
-
D.
otherTournament
Indicates a relationship where one tournament is distinct from and not the same as another tournament.
-
E.
tournamentMatches
Indicates that a tournament includes or schedules specific matches as part of its competitive structure.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:50 p.m.