Triple
T26751694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobsled Coaster |
E674555
|
entity |
| Predicate | hasRideDynamic |
P166627
|
FINISHED |
| Object | variable lateral forces |
—
|
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: variable lateral forces | Statement: [Bobsled Coaster, hasRideDynamic, variable lateral forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRideDynamic Context triple: [Bobsled Coaster, hasRideDynamic, variable lateral forces]
-
A.
hasSubRide
Indicates that a ride or journey is composed of, or includes, one or more smaller component rides or segments.
-
B.
hasRideExperience
Indicates that one entity has undergone, participated in, or possesses experience with a particular ride or riding activity in relation to another entity.
-
C.
hasRideEnvironment
Indicates that an entity is associated with, or takes place within, a particular ride-related environment or setting.
-
D.
hasRideMedium
Indicates that an entity’s ride or journey is conducted using a particular transportation medium or mode.
-
E.
hasRidingAssociation
Indicates an association where one entity is related to another through the act or context of riding (e.g., serving as rider, mount, or riding partner).
- F. None of above. chosen
Provenance (4 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_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 3:53 a.m.