Triple
T22664941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Youth Championships |
E559759
|
entity |
| Predicate | hasParticipantAgeCategory |
P110301
|
FINISHED |
| Object | youth |
—
|
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: youth | Statement: [World Youth Championships, hasParticipantAgeCategory, youth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticipantAgeCategory Context triple: [World Youth Championships, hasParticipantAgeCategory, youth]
-
A.
hasAgeParticipation
Indicates a relationship where an entity’s participation or involvement is characterized or constrained by a specific age or age range.
-
B.
hasJuniorAgeCategory
Indicates that an entity is associated with, or classified under, a junior age category within a given context or system.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
E.
hasAgeClassification
chosen
Indicates that an entity is associated with a specific age-based category 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781b3dbc8190a312843cf8c1bfc6 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.