Triple
T11095625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enchanted Airways (Singapore version planning phase) |
E262369
|
entity |
| Predicate | rideTypePlanned |
P97201
|
FINISHED |
| Object | family roller coaster |
—
|
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: family roller coaster | Statement: [Enchanted Airways (Singapore version planning phase), rideTypePlanned, family roller coaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideTypePlanned Context triple: [Enchanted Airways (Singapore version planning phase), rideTypePlanned, family roller coaster]
-
A.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
B.
transportationPlanned
Indicates that an arrangement has been made for someone or something to be transported from one place to another.
-
C.
rideModel
Indicates that one entity is a specific model or type designation of a ride associated with another entity.
-
D.
rideSystem
Indicates that one entity uses or travels on a transportation system or service provided by another entity.
-
E.
rides
Indicates that one entity travels on or is carried by another entity as a passenger or operator.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0897188190b6c293b44990b3d4 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.