Triple
T10200131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuba under-18 national baseball team |
E238859
|
entity |
| Predicate | playerAgeCategory |
P19123
|
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: [Cuba under-18 national baseball team, playerAgeCategory, youth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerAgeCategory Context triple: [Cuba under-18 national baseball team, playerAgeCategory, youth]
-
A.
ageInPlay
Indicates that an entity’s age is relevant or applicable within the context of a particular play, game, or interactive scenario.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageGroup
chosen
Indicates the categorical age range or bracket to which an entity belongs.
-
D.
raceTypeByAge
Indicates that the type or category of a race is determined or classified based on the ages of its participants.
-
E.
foundedAsAgeCategory
Indicates that an organization, group, or entity was originally established specifically to serve or represent a particular age category.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdee3f3bac8190a63a81edffe7cda7 |
completed | April 2, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8b7f348190a585daa70de4d4c8 |
completed | April 1, 2026, 8:14 p.m. |
Created at: March 30, 2026, 9:14 p.m.