Triple
T2488570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhuandhar Falls |
E55985
|
entity |
| Predicate | bestVisitTime |
P31097
|
FINISHED |
| Object | post-monsoon season |
—
|
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: post-monsoon season | Statement: [Dhuandhar Falls, bestVisitTime, post-monsoon season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestVisitTime Context triple: [Dhuandhar Falls, bestVisitTime, post-monsoon season]
-
A.
bestVisitedAt
chosen
Indicates the optimal time or conditions under which a place or entity should be visited.
-
B.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
-
C.
latestTime
Indicates the most recent point in time at which the related event, state, or condition occurs or is valid among a set of possible times.
-
D.
previousLocationTime
Indicates the specific time at which an entity was located at its immediately preceding location before its current one.
-
E.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.