Triple
T28282816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaver Meadows Entrance Station of Rocky Mountain National Park |
E713197
|
entity |
| Predicate | sideOfPark |
P33909
|
FINISHED |
| Object | east side |
—
|
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: east side | Statement: [Beaver Meadows Entrance Station of Rocky Mountain National Park, sideOfPark, east side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOfPark Context triple: [Beaver Meadows Entrance Station of Rocky Mountain National Park, sideOfPark, east side]
-
A.
parkSide
chosen
Indicates that one entity is located on the side of or adjacent to a park relative to another reference point or area.
-
B.
parkSection
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
-
C.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a park.
-
D.
parkArea
Indicates that an area of land is designated and used as a park or recreational green space.
-
E.
regionOfPark
Indicates that one entity is a geographic or administrative region that contains or is designated as a specific 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64451040881909310d73fc91bccfb |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:24 p.m.