Triple
T5130878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadhorse, Alaska |
E115694
|
entity |
| Predicate | hasWildlifeInSurroundings |
P34896
|
FINISHED |
| Object | caribou |
—
|
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: caribou | Statement: [Deadhorse, Alaska, hasWildlifeInSurroundings, caribou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeInSurroundings Context triple: [Deadhorse, Alaska, hasWildlifeInSurroundings, caribou]
-
A.
hasNearbyWildlife
chosen
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
B.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
C.
hasWildernessArea
Indicates that one entity possesses, contains, or is associated with a designated wilderness area.
-
D.
containsWildSpecies
Indicates that one entity includes, houses, or encompasses wild (non-domesticated) species within its scope or boundaries.
-
E.
containsWildernessArea
Indicates that one entity geographically includes or encompasses a designated wilderness area within its boundaries.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.