Triple
T32202951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston, Utah |
E822591
|
entity |
| Predicate | hasOutdoorTourismNearby |
P155301
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Charleston, Utah, hasOutdoorTourismNearby, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorTourismNearby Context triple: [Charleston, Utah, hasOutdoorTourismNearby, true]
-
A.
hasNaturalParkNearby
Indicates that one entity is located close to, or in the vicinity of, a natural park associated with the other entity.
-
B.
hasTouristTrails
Indicates that an entity contains or is equipped with designated paths or routes intended for use by tourists.
-
C.
hasRecreationalActivityNearby
chosen
Indicates that a location has one or more recreational activities or facilities available in its nearby surroundings.
-
D.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
E.
isHikingDestination
Indicates that a location serves as a destination or endpoint for hiking activities or routes.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 12:36 a.m.