Triple
T4018307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahanadi Delta |
E91217
|
entity |
| Predicate | riverMouthType |
P53471
|
FINISHED |
| Object | multiple distributary mouths |
—
|
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: multiple distributary mouths | Statement: [Mahanadi Delta, riverMouthType, multiple distributary mouths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMouthType Context triple: [Mahanadi Delta, riverMouthType, multiple distributary mouths]
-
A.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
B.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
C.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
D.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
E.
riverMouthElevation
Indicates the elevation at which a river reaches its mouth or endpoint, typically where it flows into another body of water.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa984948190a252eaeb9dbae454 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:35 p.m.