Triple
T6840919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niemen |
E157569
|
entity |
| Predicate | hasRiverBasinAreaApprox |
P28955
|
FINISHED |
| Object | 98,200 km² |
—
|
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: 98,200 km² | Statement: [Niemen, hasRiverBasinAreaApprox, 98,200 km²]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverBasinAreaApprox Context triple: [Niemen, hasRiverBasinAreaApprox, 98,200 km²]
-
A.
drainageBasinArea
Indicates the total surface area of land from which precipitation and runoff drain into a particular water body or watershed.
-
B.
drainageAreaApprox
chosen
Indicates that one entity has an approximate drainage area measured or characterized by the other entity.
-
C.
watershedArea
Indicates the total land area from which surface water drains into a particular water body or point in the drainage system.
-
D.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
E.
drainageAreaFeature
Indicates the geographic feature or area from which water drains into a particular water body or drainage system.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b4a1f88190b4f532828697fbd8 |
completed | March 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.