Triple
T27258212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manpura Upazila |
E687684
|
entity |
| Predicate | locatedInRiverMouthRegion |
P65228
|
FINISHED |
| Object | Meghna estuary |
—
|
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: Meghna estuary | Statement: [Manpura Upazila, locatedInRiverMouthRegion, Meghna estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRiverMouthRegion Context triple: [Manpura Upazila, locatedInRiverMouthRegion, Meghna estuary]
-
A.
riverMouthRegion
Indicates the region or area where a river flows into a larger body of water, such as a sea, lake, or another river.
-
B.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
C.
locatedInRiverDelta
chosen
Indicates that one entity is situated within the river delta region of another entity (the river).
-
D.
riverMouthAt
Indicates that the mouth or endpoint of a river is located at a specified place or geographic feature.
-
E.
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.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 27, 2026, 10:50 a.m.