Triple
T15984155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sittaung River basin |
E387647
|
entity |
| Predicate | lowerBasinTerrain |
P83395
|
FINISHED |
| Object | low-lying alluvial plain |
—
|
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: low-lying alluvial plain | Statement: [Sittaung River basin, lowerBasinTerrain, low-lying alluvial plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBasinTerrain Context triple: [Sittaung River basin, lowerBasinTerrain, low-lying alluvial plain]
-
A.
elevationLowerThan
Indicates that the elevation of one entity is lower than the elevation of another entity.
-
B.
isLowland
chosen
Indicates that an entity is located in, associated with, or characteristic of lowland areas or low-lying terrain relative to surrounding regions.
-
C.
lowerBasinAllocation
Indicates the amount of water apportioned or assigned to users located in the lower part of a river basin.
-
D.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
E.
hasInnerBasinElevationInMetres
Indicates the elevation, measured in metres, of the inner basin associated with an entity.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.