Triple
T7068892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denali Park Road |
E164631
|
entity |
| Predicate | typicalWildlifeSeen |
P34896
|
FINISHED |
| Object | grizzly bears |
—
|
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: grizzly bears | Statement: [Denali Park Road, typicalWildlifeSeen, grizzly bears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWildlifeSeen Context triple: [Denali Park Road, typicalWildlifeSeen, grizzly bears]
-
A.
hasNearbyWildlife
chosen
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
B.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
-
C.
containsWildSpecies
Indicates that one entity includes, houses, or encompasses wild (non-domesticated) species within its scope or boundaries.
-
D.
hasWildlifeIssue
Indicates that an entity is affected by, involved in, or responsible for a problem or conflict related to wildlife.
-
E.
basedOnAnimalNativeTo
Indicates that something is derived from, inspired by, or modeled after an animal that is native to a specified geographic region.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a935488190a8c9c21bf30dd5d4 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.