Triple
T25586993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiruvambady Sri Krishna Temple |
E641412
|
entity |
| Predicate | hasProcessionDuring |
P178563
|
FINISHED |
| Object | Thrissur Pooram |
—
|
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: Thrissur Pooram | Statement: [Thiruvambady Sri Krishna Temple, hasProcessionDuring, Thrissur Pooram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessionDuring Context triple: [Thiruvambady Sri Krishna Temple, hasProcessionDuring, Thrissur Pooram]
-
A.
hasProcessionFrom
Indicates that a procession, ceremony, or formal movement originates from or starts at a specified source location or entity.
-
B.
mainProcessionDay
Indicates the specific day on which the primary or central procession of an event or celebration takes place.
-
C.
organizesProcessions
Indicates that an entity is responsible for planning, coordinating, and managing the execution of processions or parades.
-
D.
mainProcessionType
Indicates the primary category or kind of procession associated with an event or context.
-
E.
ceremonialProcession
Indicates a formal, often ritualized movement of people or objects in an organized sequence as part of a ceremony or official event.
- F. None of above. chosen
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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 21, 2026, 4:17 p.m.