Triple
T35061325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fremont, Utah |
E1011597
|
entity |
| Predicate | nearPublicLands |
P73623
|
FINISHED |
| Object | Capitol Reef National Park |
—
|
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: Capitol Reef National Park | Statement: [Fremont, Utah, nearPublicLands, Capitol Reef National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearPublicLands Context triple: [Fremont, Utah, nearPublicLands, Capitol Reef National Park]
-
A.
hasNearbyPublicLand
chosen
Indicates that one entity is located close to an area of public land, such as parks, reserves, or other publicly accessible open spaces.
-
B.
isPublicLand
Indicates that a given area of land is owned or managed by a government or public authority and is accessible or designated for use by the general public.
-
C.
nearNationalForest
Indicates that one entity is located close to, but not necessarily inside, a designated national forest area.
-
D.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
E.
hasNearbyStatePark
Indicates that a location is situated close to at least one designated state park.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7860a1154819088c0faac06bc3852 |
completed | May 3, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.