Triple
T24699640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomerang Coast to Coaster |
E611694
|
entity |
| Predicate | targetRiderType |
P118952
|
FINISHED |
| Object | thrill seekers |
—
|
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: thrill seekers | Statement: [Boomerang Coast to Coaster, targetRiderType, thrill seekers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRiderType Context triple: [Boomerang Coast to Coaster, targetRiderType, thrill seekers]
-
A.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
B.
intendedRiderExperience
chosen
Indicates the type or quality of experience that is planned or designed for a rider in the context of a ride or transportation service.
-
C.
typicalRiderAgeRange
Indicates the usual or most common age range of people who ride or use something.
-
D.
primaryRiders
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
-
E.
notableRiderType
Indicates that an entity is notably associated with a particular type or category of rider (e.g., cyclist, jockey, driver).
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:22 a.m.