Triple
T11972250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitral River basin |
E284948
|
entity |
| Predicate | drainageAreaType |
P3557
|
FINISHED |
| Object | mountainous |
—
|
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: mountainous | Statement: [Chitral River basin, drainageAreaType, mountainous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageAreaType Context triple: [Chitral River basin, drainageAreaType, mountainous]
-
A.
drainageAreaFeature
Indicates the geographic feature or area from which water drains into a particular water body or drainage system.
-
B.
drainageAreaApprox
Indicates that one entity has an approximate drainage area measured or characterized by the other entity.
-
C.
drainageBasinArea
Indicates the total surface area of land from which precipitation and runoff drain into a particular water body or watershed.
-
D.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
-
E.
basinType
chosen
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.