Triple
T33224434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Gondwana basins |
E850514
|
entity |
| Predicate | majorBasin |
P36894
|
FINISHED |
| Object | Damodar Valley basin |
—
|
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: Damodar Valley basin | Statement: [Indian Gondwana basins, majorBasin, Damodar Valley basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBasin Context triple: [Indian Gondwana basins, majorBasin, Damodar Valley basin]
-
A.
basinPartOf
chosen
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
B.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
C.
hasMajorCityOnBasin
Indicates that a major city is located on or within the drainage basin of a specified water system.
-
D.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
E.
largestDrainageBasinIn
Indicates that a geographic feature has the largest drainage basin within a specified area or 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:30 a.m.