Triple
T30796703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melaghar |
E784248
|
entity |
| Predicate | riverOrWaterBodyNearby |
P8567
|
FINISHED |
| Object | Rudrasagar Lake |
—
|
NE NERFINISHED |
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: Rudrasagar Lake | Statement: [Melaghar, riverOrWaterBodyNearby, Rudrasagar Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverOrWaterBodyNearby Context triple: [Melaghar, riverOrWaterBodyNearby, Rudrasagar Lake]
-
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.
nearestLargeBodyOfWater
Indicates the closest significant body of water in proximity to a given location or entity.
-
C.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
-
D.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
E.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 8:42 p.m.