Triple
T15984154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sittaung River basin |
E387647
|
entity |
| Predicate | upperBasinTerrain |
P121166
|
FINISHED |
| Object | hilly and plateau margins |
—
|
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: hilly and plateau margins | Statement: [Sittaung River basin, upperBasinTerrain, hilly and plateau margins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperBasinTerrain Context triple: [Sittaung River basin, upperBasinTerrain, hilly and plateau margins]
-
A.
hasInnerBasinElevationInMetres
Indicates the elevation, measured in metres, of the inner basin associated with an entity.
-
B.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
C.
elevationAboveValley
Indicates the vertical height or altitude of an entity measured relative to the lowest point of the surrounding valley.
-
D.
isHighElevation
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
E.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
- 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_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. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:54 a.m.