Triple
T35597764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magh Chaturthi |
E1028681
|
entity |
| Predicate | notableCelebrationSite |
P78460
|
FINISHED |
| Object | Ganpatipule |
E313112
|
NE 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: Ganpatipule | Statement: [Magh Chaturthi, notableCelebrationSite, Ganpatipule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCelebrationSite Context triple: [Magh Chaturthi, notableCelebrationSite, Ganpatipule]
-
A.
notableCelebration
Indicates that an entity is especially recognized or distinguished for celebrating, commemorating, or observing a particular event, occasion, or practice.
-
B.
notableSiteFor
Indicates that a site is particularly recognized or distinguished for a specific feature, activity, event, or characteristic.
-
C.
notableSiteAssociatedWith
chosen
Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
-
D.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
E.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
- F. None of above.
Provenance (4 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a385bde7b808190b3c28ba160885cf2 |
completed | June 21, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.