Triple
T30796711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melaghar |
E784248
|
entity |
| Predicate | accessToNeermahal |
P17187
|
FINISHED |
| Object | boat services on Rudrasagar Lake |
—
|
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: boat services on Rudrasagar Lake | Statement: [Melaghar, accessToNeermahal, boat services on Rudrasagar Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToNeermahal Context triple: [Melaghar, accessToNeermahal, boat services on Rudrasagar Lake]
-
A.
templeAccess
Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
-
B.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
-
C.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
D.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
E.
touristAccess
chosen
Indicates that a place or resource is available for use or visitation by tourists.
- 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 8:42 p.m.