Triple
T37891277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiddi Koaster |
E945144
|
entity |
| Predicate | hasMinimumAgeFocus |
P42793
|
FINISHED |
| Object | young riders |
—
|
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: young riders | Statement: [Kiddi Koaster, hasMinimumAgeFocus, young riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinimumAgeFocus Context triple: [Kiddi Koaster, hasMinimumAgeFocus, young riders]
-
A.
hasAgeFocus
Indicates a relationship where something is characterized or distinguished by a particular age group or age-related emphasis.
-
B.
setsMinimumAge
chosen
Indicates that an entity establishes the lowest permissible age required for participation, access, or eligibility in relation to another entity or activity.
-
C.
minimumAgeInYears
Indicates the smallest number of years an entity must have lived or existed to meet a specified age requirement.
-
D.
hasMinimum
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
-
E.
ageConstraint
Indicates a restriction or condition based on the age of an entity relative to a specified threshold or range.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:19 p.m.