Triple
T10406259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahamaham tank |
E245269
|
entity |
| Predicate | festivalCrowdSize |
P18989
|
FINISHED |
| Object | large gatherings of devotees |
—
|
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: large gatherings of devotees | Statement: [Mahamaham tank, festivalCrowdSize, large gatherings of devotees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalCrowdSize Context triple: [Mahamaham tank, festivalCrowdSize, large gatherings of devotees]
-
A.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
B.
hasEventDayCrowdManagement
Indicates that specific crowd management measures or responsibilities are associated with the day on which an event takes place.
-
C.
hasCrowdLevel
chosen
Indicates the degree or intensity of how crowded a place, event, or situation is.
-
D.
floatFestivalHeldIn
Indicates that a float festival event takes place or is hosted at a specific location.
-
E.
durationOfFestivalContext
Indicates the length of time for which a festival takes place within a given contextual setting or event instance.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9e78008819088f0ffba78471509 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:08 p.m.