Triple
T28569289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieprz |
E722768
|
entity |
| Predicate | hasDrainageBasinArea |
P1641
|
FINISHED |
| Object | about 10,400 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: about 10,400 km² | Statement: [Wieprz, hasDrainageBasinArea, about 10,400 km²]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrainageBasinArea Context triple: [Wieprz, hasDrainageBasinArea, about 10,400 km²]
-
A.
drainageBasinArea
chosen
Indicates the total surface area of land from which precipitation and runoff drain into a particular water body or watershed.
-
B.
drainageAreaApprox
Indicates that one entity has an approximate drainage area measured or characterized by the other entity.
-
C.
drainageAreaFeature
Indicates the geographic feature or area from which water drains into a particular water body or drainage system.
-
D.
drainageBasin
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
-
E.
watershedArea
Indicates the total land area from which surface water drains into a particular water body or point in the 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:08 a.m.