Triple
T36313412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palampet village |
E894121
|
entity |
| Predicate | hasNearbyLakeOrTank |
P17985
|
FINISHED |
| Object | Ramappa 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: Ramappa Lake | Statement: [Palampet village, hasNearbyLakeOrTank, Ramappa Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyLakeOrTank Context triple: [Palampet village, hasNearbyLakeOrTank, Ramappa Lake]
-
A.
hasNearbyLake
chosen
Indicates that one entity is located close to or in the vicinity of a lake.
-
B.
hasNearbyLakeRegion
Indicates that one region is located close to a lake or lake-dominated area.
-
C.
hasNearbyArtificialLake
Indicates that one entity is located close to an artificial lake associated with or near another entity.
-
D.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
E.
hasLakes
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: May 3, 2026, 4:09 p.m.