Triple
T15094716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klahhane Ridge Trail |
E360508
|
entity |
| Predicate | wildlifeCommonlySeen |
P111243
|
FINISHED |
| Object | black-tailed deer |
—
|
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: black-tailed deer | Statement: [Klahhane Ridge Trail, wildlifeCommonlySeen, black-tailed deer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wildlifeCommonlySeen Context triple: [Klahhane Ridge Trail, wildlifeCommonlySeen, black-tailed deer]
-
A.
typicalWildlifeObserved
chosen
Indicates that certain wildlife species are commonly or characteristically observed in a given area or context.
-
B.
notableFaunaRegion
Indicates that a region is known for or characteristically associated with particular notable animal species.
-
C.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
D.
featuresAnimalsFrom
Indicates that one entity includes, presents, or showcases animals originating from or associated with another entity.
-
E.
faunaDiversity
Indicates the variety and richness of animal species present within a given area or ecosystem.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0054571a48190a57055c0d6e90f82 |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.