Triple
T26751687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobsled Coaster |
E674555
|
entity |
| Predicate | hasRiderRestriction |
P114807
|
FINISHED |
| Object | minimum 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: minimum height requirement | Statement: [Bobsled Coaster, hasRiderRestriction, minimum height requirement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiderRestriction Context triple: [Bobsled Coaster, hasRiderRestriction, minimum height requirement]
-
A.
hasAidRestriction
Indicates that there is a limitation or condition placed on the provision or receipt of aid between entities.
-
B.
rideRestriction
chosen
Indicates that there is a limitation or rule governing whether, how, or under what conditions one entity may ride or be transported by another.
-
C.
hasCoverageRestriction
Indicates that there is a limitation, exclusion, or condition applied to the scope or extent of coverage provided.
-
D.
hasRideRestrictionFocus
Indicates that something is specifically concerned with or centers on restrictions or limitations related to a ride.
-
E.
hasHumanUseRestriction
Indicates that there is a limitation or condition on how something may be used by humans.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 3:53 a.m.