Triple
T12930259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imphal River |
E309357
|
entity |
| Predicate | basinSupports |
P107073
|
FINISHED |
| Object | paddy cultivation in Manipur |
—
|
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: paddy cultivation in Manipur | Statement: [Imphal River, basinSupports, paddy cultivation in Manipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinSupports Context triple: [Imphal River, basinSupports, paddy cultivation in Manipur]
-
A.
basinServed
Indicates that a particular basin is supplied, drained, or otherwise functionally supported by another entity (such as a river, watershed, or infrastructure system).
-
B.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
C.
basinState
Indicates that a state contains or encompasses the drainage basin or watershed of a particular river or water system.
-
D.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
E.
formsBasinWith
Indicates that one geographic feature combines with another to create or define a shared basin or catchment area.
- F. None of above. chosen
Provenance (4 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97245b6408190816d9b7e314eb51a |
completed | April 10, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d970f6f5748190ad35aff801db53d5 |
completed | April 10, 2026, 9:51 p.m. |
Created at: April 9, 2026, 5:42 p.m.