Triple
T37783249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loopy Landscapes |
E941883
|
entity |
| Predicate | addsRideType |
P23016
|
FINISHED |
| Object | roller coasters |
—
|
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: roller coasters | Statement: [Loopy Landscapes, addsRideType, roller coasters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsRideType Context triple: [Loopy Landscapes, addsRideType, roller coasters]
-
A.
containsRideType
chosen
Indicates that one entity includes or offers a specific type or category of ride as part of its available options.
-
B.
supersededByRideType
Indicates that one ride type has been replaced or made obsolete by another ride type.
-
C.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
D.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
E.
hasRideSystem
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.