Triple
T6132977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Waves Theme & Water Park |
E136761
|
entity |
| Predicate | hasSafetyPolicy |
P31242
|
FINISHED |
| Object | ride height restrictions |
—
|
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: ride height restrictions | Statement: [Wild Waves Theme & Water Park, hasSafetyPolicy, ride height restrictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyPolicy Context triple: [Wild Waves Theme & Water Park, hasSafetyPolicy, ride height restrictions]
-
A.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
B.
hasSecurityClause
Indicates that an agreement, contract, or document includes a provision specifying security-related requirements, protections, or safeguards.
-
C.
hasNotablePolicy
chosen
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
-
D.
hasSafetyCertificate
Indicates that an entity possesses or has been granted a valid safety certificate.
-
E.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c509848819089a2b2b58744bc25 |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.