Triple
T22725415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black River (King County, Washington) |
E561978
|
entity |
| Predicate | currentUseOfRemnantArea |
P16008
|
FINISHED |
| Object | wildlife habitat |
—
|
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: wildlife habitat | Statement: [Black River (King County, Washington), currentUseOfRemnantArea, wildlife habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentUseOfRemnantArea Context triple: [Black River (King County, Washington), currentUseOfRemnantArea, wildlife habitat]
-
A.
remnantRegion
Indicates that a region is a leftover or remaining part of something that previously existed or was larger.
-
B.
currentSiteUse
chosen
Indicates how a site is presently being used or the function it currently serves.
-
C.
usedRegion
Indicates that an entity operates in, applies to, or is utilized within a specified geographic or administrative region.
-
D.
usedBaseArea
Indicates that one entity makes use of the base area (surface or footprint) of another entity for its function or calculation.
-
E.
primaryCurrentUse
Indicates the main way something is currently being used or its principal present function.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17929710c81909a895622ee32920e |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:20 p.m.