Triple
T37130309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adventure Cove Waterpark |
E919497
|
entity |
| Predicate | typeOfWaterPark |
P57712
|
FINISHED |
| Object | marine-themed water park |
—
|
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: marine-themed water park | Statement: [Adventure Cove Waterpark, typeOfWaterPark, marine-themed water park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWaterPark Context triple: [Adventure Cove Waterpark, typeOfWaterPark, marine-themed water park]
-
A.
waterParkType
chosen
Indicates the specific type or category of a water park associated with an entity.
-
B.
waterRideCategory
Indicates that an attraction or ride belongs to a category specifically associated with water-based rides or experiences.
-
C.
waterParkSectionType
Indicates the specific type or category of a section within a water park (e.g., ride area, kids zone, relaxation area).
-
D.
amusementParkType
Indicates that one entity is classified as a specific type or category of amusement park in relation to another entity.
-
E.
hasWaterRide
Indicates that an entity features or includes at least one water-based ride or attraction.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a035052a47081908e9e56e21c543d46 |
completed | May 12, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_6a034d306e588190a2dce906fd46eb54 |
completed | May 12, 2026, 3:54 p.m. |
Created at: May 3, 2026, 4:15 p.m.