Triple
T34805474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radha Rani Temple |
E1003340
|
entity |
| Predicate | festivalAttraction |
P96461
|
FINISHED |
| Object | Lathmar Holi celebrations |
—
|
NE NERFINISHED |
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: Lathmar Holi celebrations | Statement: [Radha Rani Temple, festivalAttraction, Lathmar Holi celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalAttraction Context triple: [Radha Rani Temple, festivalAttraction, Lathmar Holi celebrations]
-
A.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
B.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
C.
festivalFeature
chosen
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
D.
hasFestivalAttraction
Indicates that a festival includes or features a particular attraction as part of its offerings.
-
E.
festivalFunction
Indicates that an event serves as a festival or is functioning in the role of a festival within a given context.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.