Triple
T1021546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantasilandia |
E22049
|
entity |
| Predicate | hasRideType |
P8076
|
FINISHED |
| Object | steel 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: steel roller coaster | Statement: [Fantasilandia, hasRideType, steel roller coaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRideType Context triple: [Fantasilandia, hasRideType, steel roller coaster]
-
A.
rideType
chosen
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
B.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
D.
fareType
Indicates the category or class of fare (such as standard, discounted, or promotional) that applies to a given trip, ticket, or pricing instance.
-
E.
fareTypes
Indicates the categories or kinds of fares (e.g., ticket or pricing options) that apply to a given travel or service offering.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7dead9c8190a0f8d4ef48e6c809 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b724c7908190a5b92a57fbdbff4e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.