Triple
T543331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney's Polynesian Village Resort |
E12678
|
entity |
| Predicate | hasAccommodationType |
P2836
|
FINISHED |
| Object | standard hotel rooms |
—
|
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: standard hotel rooms | Statement: [Disney's Polynesian Village Resort, hasAccommodationType, standard hotel rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccommodationType Context triple: [Disney's Polynesian Village Resort, hasAccommodationType, standard hotel rooms]
-
A.
hasResortHotel
Indicates that one entity owns, includes, or is associated with a resort hotel as part of its facilities or offerings.
-
B.
hasCabins
Indicates that an entity possesses or includes one or more cabins as part of its structure or facilities.
-
C.
hasAttractionType
Indicates that one entity is associated with a specific kind or category of attraction (e.g., tourist, cultural, natural).
-
D.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
E.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4986250508190ac91cfdf7d57073d |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.