Triple
T20114793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamunda Devi Temple |
E490428
|
entity |
| Predicate | nearbyRiverOrStream |
P8567
|
FINISHED |
| Object | Baner Khad |
—
|
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: Baner Khad | Statement: [Chamunda Devi Temple, nearbyRiverOrStream, Baner Khad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyRiverOrStream Context triple: [Chamunda Devi Temple, nearbyRiverOrStream, Baner Khad]
-
A.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
B.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
C.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
D.
nearbyWaterfall
Indicates that the entity is located close to or within a short distance of a waterfall.
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e3f2288190840d1eb431ac9a1b |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.