Triple
T17147301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teamboat Springs |
E416122
|
entity |
| Predicate | partOfResortComplex |
P60302
|
FINISHED |
| Object | Walt Disney World Resort water parks |
—
|
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: Walt Disney World Resort water parks | Statement: [Teamboat Springs, partOfResortComplex, Walt Disney World Resort water parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfResortComplex Context triple: [Teamboat Springs, partOfResortComplex, Walt Disney World Resort water parks]
-
A.
partOfResortComplexWith
chosen
Indicates that one entity is a component or facility within the same resort complex as the other entity, forming part of a shared resort property.
-
B.
partOfResortCategory
Indicates that something belongs to, or is classified within, a specific resort category.
-
C.
partOfSkiArea
Indicates that one entity is a component or subdivision within a larger ski area.
-
D.
partOfTerminalComplex
Indicates that an entity functions as a component or subunit within a larger terminal complex structure.
-
E.
housedWithinComplex
Indicates that one entity is located inside and functionally part of a larger building or facility complex.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2db20d48190b5d69ccf89f3bc42 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.