Triple
T23215179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bikin River |
E580714
|
entity |
| Predicate | valleyLandCover |
P9701
|
FINISHED |
| Object | old-growth conifer-broadleaf forests |
—
|
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: old-growth conifer-broadleaf forests | Statement: [Bikin River, valleyLandCover, old-growth conifer-broadleaf forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valleyLandCover Context triple: [Bikin River, valleyLandCover, old-growth conifer-broadleaf forests]
-
A.
drainageBasinLandCover
Indicates the type or characteristics of land cover present within a drainage basin area.
-
B.
drainageBasinLandUse
Indicates how the land within a drainage basin is utilized or managed (e.g., for agriculture, urban development, or natural vegetation).
-
C.
vegetationCoverage
Indicates the extent or proportion of an area that is covered by vegetation.
-
D.
forestCoverCharacteristic
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
-
E.
landscapeType
chosen
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191646c548190a3f7150f0c253dc1 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.