Triple
T26980338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brihadeeswara |
E679583
|
entity |
| Predicate | hasPrimaryRegionOfWorship |
P23627
|
FINISHED |
| Object | South India |
—
|
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: South India | Statement: [Brihadeeswara, hasPrimaryRegionOfWorship, South India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRegionOfWorship Context triple: [Brihadeeswara, hasPrimaryRegionOfWorship, South India]
-
A.
majorRegionOfWorship
chosen
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
B.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
C.
placeOfWorshipLocation
Indicates the location where a particular place of worship is situated or found.
-
D.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
E.
centralActOfWorshipOf
Indicates that one entity serves as the primary or most important act of worship directed toward another entity.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 27, 2026, 6:45 a.m.