Triple
T8088427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perur Pateeswarar Temple |
E188793
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Perur |
E337851
|
NE 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: Perur | Statement: [Perur Pateeswarar Temple, locatedIn, Perur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Perur Context triple: [Perur Pateeswarar Temple, locatedIn, Perur]
-
A.
Perur
chosen
Perur is a historic locality near Coimbatore in Tamil Nadu, India, known for its ancient temples and cultural significance.
-
B.
Perron
Perron is a surname of French origin, often considered a variant of the name Perrin.
-
C.
Perast
Perast is a historic coastal town in Montenegro renowned for its well-preserved Baroque architecture and picturesque setting on the Bay of Kotor.
-
D.
Pervyse
Pervyse is a village in West Flanders, Belgium, known for its location on the World War I Yser Front and the heavy fighting that took place there.
-
E.
Per
Per is a Scandinavian masculine given name, commonly used in Norway, Sweden, and Denmark as a form of Peter.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421c717c819089dd88c30a6401aa |
completed | March 31, 2026, 3:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc6406395c8190ad8db69c878ce9b8 |
completed | April 1, 2026, 12:17 a.m. |
Created at: March 30, 2026, 5:29 p.m.