Triple
T10387323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DreamWorks Theatre Featuring Kung Fu Panda |
E244794
|
entity |
| Predicate | singleRiderAvailable |
P30894
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [DreamWorks Theatre Featuring Kung Fu Panda, singleRiderAvailable, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleRiderAvailable Context triple: [DreamWorks Theatre Featuring Kung Fu Panda, singleRiderAvailable, no]
-
A.
hasSingleRiderLine
chosen
Indicates that a ride or attraction offers a dedicated line for solo riders, separate from the regular queue.
-
B.
managedRider
Indicates that one entity was responsible for directing, organizing, or overseeing the activities or career of a rider.
-
C.
hasOwnerRider
Indicates that an entity (such as an animal or vehicle) has a specific person who both owns it and rides or uses it.
-
D.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
E.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a4e6748190bd9dd319de94c659 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:05 p.m.