Triple
T28114496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachainayaki |
E710582
|
entity |
| Predicate | templeRegion |
P162532
|
FINISHED |
| Object | Coimbatore region |
—
|
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: Coimbatore region | Statement: [Pachainayaki, templeRegion, Coimbatore region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeRegion Context triple: [Pachainayaki, templeRegion, Coimbatore region]
-
A.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
-
B.
templeCountry
Indicates that a temple is located within or belongs to a particular country.
-
C.
shrineRegion
chosen
Indicates that a shrine is located within or associated with a particular geographic region.
-
D.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
E.
hasTempleDistrict
Indicates that a place or settlement contains or is associated with a designated temple district area.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 9:13 p.m.