Triple
T20275818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humunga Kowabunga |
E503011
|
entity |
| Predicate | parkCategory |
P12265
|
FINISHED |
| Object | water park attraction |
—
|
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: water park attraction | Statement: [Humunga Kowabunga, parkCategory, water park attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkCategory Context triple: [Humunga Kowabunga, parkCategory, water park attraction]
-
A.
parkType
chosen
Indicates the specific category or classification of a park based on its designated use, management, or characteristics.
-
B.
parkAreaType
Indicates the classification of a park’s area according to its designated type or functional category.
-
C.
parkArea
Indicates that an area of land is designated and used as a park or recreational green space.
-
D.
parkEstablishmentPurpose
Indicates the intended purpose or primary reason for which a park was established.
-
E.
parkSection
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e3df68819096fb859bc92a0da1 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:32 a.m.