Triple
T35980646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SKPD |
E1040552
|
entity |
| Predicate | servesRiverRegion |
P200691
|
FINISHED |
| Object | Inírida River area |
—
|
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: Inírida River area | Statement: [SKPD, servesRiverRegion, Inírida River area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRiverRegion Context triple: [SKPD, servesRiverRegion, Inírida River area]
-
A.
servesBasin
chosen
Indicates that one entity functions to provide service or support to a particular basin or drainage area.
-
B.
servesBankOfRiver
Indicates that something functions to support, protect, or maintain the bank of a river.
-
C.
primaryRiverRegion
Indicates that a given region is the main geographic area through which a particular river primarily flows or with which it is chiefly associated.
-
D.
isRegionalRiver
Indicates that a river is classified as a regional river, typically limited in geographic extent and significance to a specific region rather than being a major or national waterway.
-
E.
basinServed
Indicates that a particular basin is supplied, drained, or otherwise functionally supported by another entity (such as a river, watershed, or infrastructure 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: May 3, 2026, 4:07 p.m.