Triple
T38269055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manjinikkara |
E1021151
|
entity |
| Predicate | hasAnnualPilgrimage |
P73017
|
FINISHED |
| Object | Manjinikkara Perunnal |
—
|
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: Manjinikkara Perunnal | Statement: [Manjinikkara, hasAnnualPilgrimage, Manjinikkara Perunnal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnnualPilgrimage Context triple: [Manjinikkara, hasAnnualPilgrimage, Manjinikkara Perunnal]
-
A.
pilgrimageFrequency
Indicates how often an entity undertakes or participates in a pilgrimage.
-
B.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
C.
hasPilgrimageActivity
chosen
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
-
D.
pilgrimageSince
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
-
E.
hasPilgrimageFocus
Indicates that something is centered on, dedicated to, or primarily concerned with religious or spiritual pilgrimage activities or themes.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:30 p.m.