Triple
T32461390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgium national youth football teams |
E829582
|
entity |
| Predicate | worldTournaments |
P41684
|
FINISHED |
| Object | FIFA U-17 World Cup |
—
|
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: FIFA U-17 World Cup | Statement: [Belgium national youth football teams, worldTournaments, FIFA U-17 World Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldTournaments Context triple: [Belgium national youth football teams, worldTournaments, FIFA U-17 World Cup]
-
A.
worldTournament
chosen
Indicates a competitive event or series of contests held at a global level, typically involving participants from multiple countries.
-
B.
otherTournament
Indicates a relationship where one tournament is distinct from and not the same as another tournament.
-
C.
WorldChampionshipsEvent
Indicates an event that is part of, or constitutes, a world-level championship competition.
-
D.
worldChampionshipChallenger
Indicates that an entity has qualified to challenge the reigning world champion in a given competition or discipline.
-
E.
tournamentContinentScope
Indicates that a tournament’s scope or coverage is defined at the level of an entire continent.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 12:57 a.m.