Triple
T21459319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Splish Splash water park |
E529427
|
entity |
| Predicate | hasHeightRestrictions |
P8078
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Splish Splash water park, hasHeightRestrictions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightRestrictions Context triple: [Splish Splash water park, hasHeightRestrictions, true]
-
A.
heightRestriction
chosen
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
heightRestrictionWithCompanion
Indicates that there is a height-based restriction which may be satisfied or modified when the person is accompanied by a qualifying companion.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
estimatedHeadHeightInMeters
Indicates the estimated vertical height of a person's head, measured in meters.
-
E.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ed36c08190a5178b2308aca8da |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:08 p.m.