Triple
T24154845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shariatpur District |
E598645
|
entity |
| Predicate | riverineLandscape |
P93533
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shariatpur District, riverineLandscape, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverineLandscape Context triple: [Shariatpur District, riverineLandscape, true]
-
A.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
B.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
-
C.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
D.
watercourseFeature
chosen
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
-
E.
riverFormed
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e4372081909d2b3f7f2af7b407 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:31 p.m.