Triple
T37589413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son River basin |
E935216
|
entity |
| Predicate | flowsThroughPhysiographicRegion |
P89063
|
FINISHED |
| Object | Vindhyan plateau |
—
|
NE NERFINISHED |
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: Vindhyan plateau | Statement: [Son River basin, flowsThroughPhysiographicRegion, Vindhyan plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsThroughPhysiographicRegion Context triple: [Son River basin, flowsThroughPhysiographicRegion, Vindhyan plateau]
-
A.
watercourseThroughRegion
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
-
B.
flowsIntoEcoregion
Indicates that a body of water or watercourse moves into and enters the boundaries of a specified ecoregion.
-
C.
flowsToBodyOfWater
Indicates that a fluid or water source moves or is directed into a specified body of water.
-
D.
flowsThroughLandscape
Indicates that something (typically a fluid or moving entity) passes through or traverses a particular landscape or terrain.
-
E.
flowsThroughRegionType
chosen
Indicates that something such as a fluid, current, or pathway passes through and traverses a specified type of region.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.