Triple
T2621968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandora – The World of Avatar |
E59028
|
entity |
| Predicate | rideSystemUsed |
P23569
|
FINISHED |
| Object | simulator ride system |
—
|
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: simulator ride system | Statement: [Pandora – The World of Avatar, rideSystemUsed, simulator ride system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideSystemUsed Context triple: [Pandora – The World of Avatar, rideSystemUsed, simulator ride system]
-
A.
rideSystem
Indicates that one entity uses or travels on a transportation system or service provided by another entity.
-
B.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
C.
hasRideSystem
chosen
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
-
D.
bicycleType
Indicates the specific kind or category of bicycle associated with an entity.
-
E.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.