Triple
T15158470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niyodo River basin |
E362143
|
entity |
| Predicate | riverLengthOfMainRiver_km |
P59548
|
FINISHED |
| Object | approximately 124 |
—
|
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: approximately 124 | Statement: [Niyodo River basin, riverLengthOfMainRiver_km, approximately 124]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverLengthOfMainRiver_km Context triple: [Niyodo River basin, riverLengthOfMainRiver_km, approximately 124]
-
A.
waterwayLengthKilometres
chosen
Indicates the total length of a waterway, measured in kilometres.
-
B.
hasLongestRiver
Indicates that one entity possesses or contains the river that is longer than any other river associated with the compared entities.
-
C.
largestInflowRiver
Indicates that one river has the greatest volume of water flowing into a specified body (such as a lake, sea, or another river) compared to all other contributing rivers.
-
D.
isSecondLongestRiverIn
Indicates that a river is the second longest river within a specified geographic region or entity.
-
E.
isLongestRiverEntirelyIn
Indicates that a river is the longest one whose entire course lies within a specified geographic region or political entity.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060dd71881908ecc4a4f52d438a5 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.