Triple
T25608113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Highway 82 (Colorado) |
E641967
|
entity |
| Predicate | servesResortTown |
P84905
|
FINISHED |
| Object | Aspen, Colorado |
—
|
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: Aspen, Colorado | Statement: [State Highway 82 (Colorado), servesResortTown, Aspen, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesResortTown Context triple: [State Highway 82 (Colorado), servesResortTown, Aspen, Colorado]
-
A.
servesResortArea
chosen
Indicates that one entity provides services or operational support to a resort area.
-
B.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
C.
locatedInResortTown
Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
-
D.
isResortDestinationFor
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
-
E.
servesTownship
Indicates that an entity provides official services or administrative functions to a particular township.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 21, 2026, 4:39 p.m.