Triple
T9831674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavadee |
E238999
|
entity |
| Predicate | locationOfWorship |
P1191
|
FINISHED |
| Object | Murugan temples in Mauritius |
—
|
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: Murugan temples in Mauritius | Statement: [Cavadee, locationOfWorship, Murugan temples in Mauritius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfWorship Context triple: [Cavadee, locationOfWorship, Murugan temples in Mauritius]
-
A.
hasPlaceOfWorship
chosen
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
B.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
C.
centralActOfWorshipOf
Indicates that one entity serves as the primary or most important act of worship directed toward another entity.
-
D.
countryOfWorshipSite
Indicates that a place of worship is located within the borders of a specified country.
-
E.
majorRegionOfWorship
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb335623c8190902de29795bce87d |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.