Triple
T32181025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay of Bengal shoreline |
E821981
|
entity |
| Predicate | hasMajorDelta |
P202408
|
FINISHED |
| Object | Ganges-Brahmaputra-Meghna delta |
E150721
|
NE 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: Ganges-Brahmaputra-Meghna delta | Statement: [Bay of Bengal shoreline, hasMajorDelta, Ganges-Brahmaputra-Meghna delta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorDelta Context triple: [Bay of Bengal shoreline, hasMajorDelta, Ganges-Brahmaputra-Meghna delta]
-
A.
hasDelta
Indicates that there is a change, difference, or deviation between two related states, values, or versions of something.
-
B.
hasNotableDelta
Indicates that there is a significant or noteworthy change or difference between two compared entities or states.
-
C.
hasMajorUpgrade
Indicates that an entity has received a significant or substantial upgrade relative to its previous state.
-
D.
hasDeltaType
Indicates that one entity is associated with a specific type or category of change (delta) relative to another entity or state.
-
E.
containsDelta
Indicates that one entity includes or encompasses a change, difference, or delta associated with another entity.
- F. None of above. chosen
Provenance (5 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0be2d1388190aa46704c20c1ea08 |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
| PDg | Predicate description generation | batch_6a007aa82810819080bb16dd5022c324 |
completed | May 10, 2026, 12:31 p.m. |
Created at: May 1, 2026, 12:34 a.m.