Triple
T35480748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baleshwar Temple, Champawat |
E1025462
|
entity |
| Predicate | hasCarvingTheme |
P155340
|
FINISHED |
| Object | Hindu deities |
—
|
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: Hindu deities | Statement: [Baleshwar Temple, Champawat, hasCarvingTheme, Hindu deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarvingTheme Context triple: [Baleshwar Temple, Champawat, hasCarvingTheme, Hindu deities]
-
A.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
-
B.
carvingTheme
chosen
Indicates that one entity features another entity as the subject or motif of its carved decoration.
-
C.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
D.
hasCarvingType
Indicates that one entity is associated with a specific type or style of carving applied to it.
-
E.
isCarvedWith
Indicates that one entity has been shaped, decorated, or formed by carving using another entity as the tool, method, or material.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.