Triple
T16211432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cave Train |
E393474
|
entity |
| Predicate | hasRideEnvironment |
P122177
|
FINISHED |
| Object | enclosed show building |
—
|
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: enclosed show building | Statement: [Cave Train, hasRideEnvironment, enclosed show building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRideEnvironment Context triple: [Cave Train, hasRideEnvironment, enclosed show building]
-
A.
hasRideSystem
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
-
B.
hasRideExperience
Indicates that one entity has undergone, participated in, or possesses experience with a particular ride or riding activity in relation to another entity.
-
C.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
-
D.
hasSubRide
Indicates that a ride or journey is composed of, or includes, one or more smaller component rides or segments.
-
E.
hasDarkRide
Indicates that one entity features or includes a dark ride attraction associated with the other entity.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.