Triple
T6835009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Athletes |
E157426
|
entity |
| Predicate | servesChildrenWith |
P33500
|
FINISHED |
| Object | intellectual disabilities |
—
|
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: intellectual disabilities | Statement: [Young Athletes, servesChildrenWith, intellectual disabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesChildrenWith Context triple: [Young Athletes, servesChildrenWith, intellectual disabilities]
-
A.
childrenWith
Indicates that two or more entities share one or more children together as parents or guardians.
-
B.
hasKidsMenu
Indicates that an establishment offers a menu specifically designed for children.
-
C.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
D.
intendedToServe
chosen
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
E.
servesMostly
Indicates that one entity primarily functions to serve, support, or cater to another entity, more than to any other.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67a9ff88190b0d86331b3ea06aa |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.