Triple
T27828652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Petroleum Reserve–Alaska |
E703026
|
entity |
| Predicate | notableWildlifeHabitat |
P92447
|
FINISHED |
| Object | Teshekpuk Lake area |
—
|
NE NERFINISHED |
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: Teshekpuk Lake area | Statement: [National Petroleum Reserve–Alaska, notableWildlifeHabitat, Teshekpuk Lake area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWildlifeHabitat Context triple: [National Petroleum Reserve–Alaska, notableWildlifeHabitat, Teshekpuk Lake area]
-
A.
habitatOfNotableSpecies
Indicates that a location serves as the natural environment or living area for one or more notable species.
-
B.
hasWildlifeHabitats
chosen
Indicates that an entity contains or supports natural environments where wildlife species live, feed, or reproduce.
-
C.
naturalReservoirOfNotableSpecies
Indicates that a location serves as a natural habitat or reservoir for one or more notable species.
-
D.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
E.
notableFaunaRegion
Indicates that a region is known for or characteristically associated with particular notable animal species.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: April 27, 2026, 5:54 p.m.