Triple
T30333613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanthimathi Amman Temple |
E771553
|
entity |
| Predicate | hasPilgrimType |
P170451
|
FINISHED |
| Object | local 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: local devotees | Statement: [Kanthimathi Amman Temple, hasPilgrimType, local devotees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimType Context triple: [Kanthimathi Amman Temple, hasPilgrimType, local devotees]
-
A.
hasPilgrimageType
Indicates that an entity is associated with a specific type or category of pilgrimage.
-
B.
isPilgrimTo
Indicates that one entity travels to or visits a place as a religious or spiritual pilgrimage in relation to another entity.
-
C.
hasPilgrims
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
-
D.
hasPilgrimageRouteType
Indicates that a pilgrimage route is associated with a specific type or category of pilgrimage path.
-
E.
hasPilgrimageObject
Indicates that an entity has a specific object or site that serves as the focus or destination of a pilgrimage associated with it.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 29, 2026, 7:53 p.m.