Triple
T9200919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neermahal Palace |
E220834
|
entity |
| Predicate | regionOfLake |
P85470
|
FINISHED |
| Object | western bank of Rudrasagar Lake (for access) |
—
|
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: western bank of Rudrasagar Lake (for access) | Statement: [Neermahal Palace, regionOfLake, western bank of Rudrasagar Lake (for access)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfLake Context triple: [Neermahal Palace, regionOfLake, western bank of Rudrasagar Lake (for access)]
-
A.
mouthLake
Indicates the location where a river or stream flows into and forms part of a lake.
-
B.
isInLake
Indicates that one entity is located within the body of water defined as a lake.
-
C.
bordersLake
chosen
Indicates that one entity is directly adjacent to and shares a boundary with a lake.
-
D.
locatedInLakeRegion
Indicates that the subject entity is situated within a geographic area characterized as a lake region.
-
E.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or entity.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9429b448190a078e9cdfedd4918 |
completed | April 1, 2026, 8:37 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.