Triple
T16820775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Wolf Lodge Concord |
E408882
|
entity |
| Predicate | allowsAccessToWaterPark |
P62705
|
FINISHED |
| Object | for registered overnight guests |
—
|
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: for registered overnight guests | Statement: [Great Wolf Lodge Concord, allowsAccessToWaterPark, for registered overnight guests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsAccessToWaterPark Context triple: [Great Wolf Lodge Concord, allowsAccessToWaterPark, for registered overnight guests]
-
A.
hasWaterPark
Indicates that one entity possesses, includes, or features a water park as part of its facilities or attributes.
-
B.
hasWaterRide
Indicates that an entity features or includes at least one water-based ride or attraction.
-
C.
hasParkAccess
chosen
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
D.
swimmingAllowed
Indicates that swimming is permitted at a particular place, time, or under specified conditions.
-
E.
themeParkAccess
Indicates that an entity has permission or eligibility to enter or use the facilities and attractions of a theme 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e6b59c8190ad562a80e71ce54c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.