Triple

T34612003
Position Surface form Disambiguated ID Type / Status
Subject Cedar River Village E888763 entity
Predicate isWithinResortComplex P60302 FINISHED
Object Shanty Creek Resorts NE NERFINISHED

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: Shanty Creek Resorts | Statement: [Cedar River Village, isWithinResortComplex, Shanty Creek Resorts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isWithinResortComplex
Context triple: [Cedar River Village, isWithinResortComplex, Shanty Creek Resorts]
  • A. isWithinResort
    Indicates that one place, object, or activity is located inside the boundaries of a specific resort.
  • B. 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.
  • C. isResortOf
    Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
  • D. containsResortArea
    Indicates that one location or region includes within its boundaries a designated resort area.
  • E. locatedInResortTown
    Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
  • 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_69f349d584e08190b40b9f6281ad50c4 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7234bcaa48190ac970759d34e254a completed May 3, 2026, 10:28 a.m.
PD Predicate disambiguation batch_69f72155c48881909bd40b9aa3febd5a completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 2:03 a.m.