Triple
T24656523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajaraja I |
E610406
|
entity |
| Predicate | templeCommissioned |
P67282
|
FINISHED |
| Object | Siva temple at Thiruvaiyaru |
—
|
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: Siva temple at Thiruvaiyaru | Statement: [Rajaraja I, templeCommissioned, Siva temple at Thiruvaiyaru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeCommissioned Context triple: [Rajaraja I, templeCommissioned, Siva temple at Thiruvaiyaru]
-
A.
plannedTempleDedicatedBy
Indicates that a temple, while still in the planning or unbuilt stage, is intended or designated to be dedicated by a specific agent or entity.
-
B.
templeDedicatedBy
Indicates that a temple was formally dedicated, consecrated, or established by a specific person, group, or authority.
-
C.
foundedTemple
Indicates that an entity established or created a temple, typically as its founder.
-
D.
templeConstruction
chosen
Indicates the action or process of building, erecting, or establishing a temple or similar sacred structure.
-
E.
constructionOfMainTempleCompleted
Indicates that the primary temple’s construction process has been fully completed.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 2:34 a.m.