Triple
T23500737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuribey River |
E571832
|
entity |
| Predicate | hasMainLandCoverInBasin |
P116511
|
FINISHED |
| Object | tundra vegetation |
—
|
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: tundra vegetation | Statement: [Yuribey River, hasMainLandCoverInBasin, tundra vegetation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLandCoverInBasin Context triple: [Yuribey River, hasMainLandCoverInBasin, tundra vegetation]
-
A.
hasWaterBasins
Indicates that one entity possesses, contains, or includes one or more water basins in relation to another entity.
-
B.
drainageBasinLandCover
chosen
Indicates the type or characteristics of land cover present within a drainage basin area.
-
C.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
D.
hasRiparianZone
Indicates that an area is adjacent to and ecologically influenced by a body of water, forming its riparian (riverbank or shoreline) zone.
-
E.
hasMajorOutflowBasin
Indicates that a geographic feature (such as a water body or watershed) has a specific basin into which most or all of its water ultimately flows.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a8fc37908190af86a01ab85737d6 |
completed | April 29, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:06 p.m.