Triple
T22755493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranakpur Jain temple |
E562831
|
entity |
| Predicate | pillarCarvings |
P48945
|
FINISHED |
| Object | figures of 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: figures of deities | Statement: [Ranakpur Jain temple, pillarCarvings, figures of deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pillarCarvings Context triple: [Ranakpur Jain temple, pillarCarvings, figures of deities]
-
A.
hasFrontCarvings
Indicates that an object or structure features carvings or sculpted details on its front-facing surface.
-
B.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
-
C.
hasCarvings
chosen
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
D.
hasBackCarvings
Indicates that an entity possesses carvings or engraved markings specifically located on its back.
-
E.
hasTrunkCarvings
Indicates that an entity (typically a tree) possesses carvings or engravings on its trunk.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bc48788190b3deb9287d02cb2c |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.