Triple
T27145843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daulatkhan Upazila |
E681939
|
entity |
| Predicate | hasRiverineCharacter |
P128972
|
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: [Daulatkhan Upazila, hasRiverineCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverineCharacter Context triple: [Daulatkhan Upazila, hasRiverineCharacter, true]
-
A.
hasRiverineCharacteristic
chosen
Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
D.
hasRiverInfluence
Indicates that one entity affects or is affected by a river in terms of its characteristics, behavior, or conditions.
-
E.
hasAncestralRiver
Indicates that an entity is associated with or originates from a river regarded as its ancestral or traditional source.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 9:11 a.m.