Triple
T22473161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badwani |
E555556
|
entity |
| Predicate | hasNotableRiverFeature |
P128972
|
FINISHED |
| Object | Narmada riverbank |
—
|
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: Narmada riverbank | Statement: [Badwani, hasNotableRiverFeature, Narmada riverbank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRiverFeature Context triple: [Badwani, hasNotableRiverFeature, Narmada riverbank]
-
A.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
B.
hasRiverineCharacteristic
chosen
Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
-
C.
hasWaterFeatures
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
-
D.
hasFictionalRiver
Indicates that an entity includes, features, or is associated with a river that is fictional rather than real.
-
E.
isOnlyNavigableRiverOf
Indicates that one river is the sole river that can be navigated within a specified area or context.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be2034c81909d1263f2ed114b46 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.