Triple
T17147380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downhill Double Dipper |
E416124
|
entity |
| Predicate | hasMinimumAgePolicy |
P42793
|
FINISHED |
| Object | based on height requirement |
—
|
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: based on height requirement | Statement: [Downhill Double Dipper, hasMinimumAgePolicy, based on height requirement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinimumAgePolicy Context triple: [Downhill Double Dipper, hasMinimumAgePolicy, based on height requirement]
-
A.
setsMinimumAge
chosen
Indicates that an entity establishes the lowest permissible age required for participation, access, or eligibility in relation to another entity or activity.
-
B.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
-
C.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
D.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
E.
hasLowerAge
Indicates that one entity is younger in age than 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f404f0e88190b7ac9ac523fdc7da |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.