Triple
T9667377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-17 |
E233739
|
entity |
| Predicate | usedInCompetitionType |
P80731
|
FINISHED |
| Object | international youth football competitions |
—
|
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: international youth football competitions | Statement: [U-17, usedInCompetitionType, international youth football competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCompetitionType Context triple: [U-17, usedInCompetitionType, international youth football competitions]
-
A.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
-
B.
usedInCompetitionContext
chosen
Indicates that something is employed or occurs within the setting, rules, or circumstances of a competition or contest.
-
C.
usesCompetitionSystem
Indicates that an entity operates under or applies a particular competition system or format.
-
D.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
E.
competitionUse
Indicates that one entity uses or engages in a competition involving another entity.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3c06e4819080c1b8e66faa482f |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.