Triple
T2460646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maheshwar Ghat |
E54524
|
entity |
| Predicate | hasTimeOfHighFootfall |
P35231
|
FINISHED |
| Object | Hindu festivals |
—
|
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: Hindu festivals | Statement: [Maheshwar Ghat, hasTimeOfHighFootfall, Hindu festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeOfHighFootfall Context triple: [Maheshwar Ghat, hasTimeOfHighFootfall, Hindu festivals]
-
A.
hasFootfallPattern
Indicates a characteristic pattern or sequence of steps, movements, or impacts made by an entity’s feet during locomotion or activity.
-
B.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
-
C.
hasHeavyPassengerTraffic
chosen
Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
-
D.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
E.
hasDailyPassengerTraffic
Indicates the number of passengers that regularly use or pass through something (such as a station or route) each day.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.