Triple
T28466156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mary Valley |
E720297
|
entity |
| Predicate | locatedInPartOfPark |
P38797
|
FINISHED |
| Object | eastern Glacier National Park |
—
|
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: eastern Glacier National Park | Statement: [St. Mary Valley, locatedInPartOfPark, eastern Glacier National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPartOfPark Context triple: [St. Mary Valley, locatedInPartOfPark, eastern Glacier National Park]
-
A.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a park.
-
B.
locatedInNationalOrProvincialPark
Indicates that one entity is situated within the boundaries of a national or provincial park.
-
C.
partOfChainOfParks
Indicates that an entity is one segment or component within a connected sequence of parks or green spaces.
-
D.
isWithinPark
chosen
Indicates that one entity is located inside the boundaries of a park that contains it.
-
E.
locatedInParkLikeSetting
Indicates that something is situated within or directly surrounded by an environment resembling a park, typically featuring natural or landscaped outdoor elements.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: April 28, 2026, 2:45 a.m.