Triple
T18527502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohyah Drop Slide |
E452755
|
entity |
| Predicate | launchesRidersInto |
P17680
|
FINISHED |
| Object | splash pool |
—
|
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: splash pool | Statement: [Ohyah Drop Slide, launchesRidersInto, splash pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchesRidersInto Context triple: [Ohyah Drop Slide, launchesRidersInto, splash pool]
-
A.
firstRider
Indicates that one entity is the first rider in relation to another entity, typically marking the earliest or primary participant in a riding-related context.
-
B.
laterRider
Indicates that one rider or passenger occurs or appears later in time than another rider or passenger within a given context or sequence.
-
C.
numberOfRiders
Indicates the total count of riders associated with a given entity or event.
-
D.
launchesTo
chosen
Indicates that one entity initiates the sending or propulsion of another entity toward a specific destination or into a particular trajectory.
-
E.
launchesOver
Indicates that one entity propels or sends another entity in a trajectory that passes above or over a third entity or reference point.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533f9bd1081909743b24e290b7dfe |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.