Triple
T18836878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandariya Mahadeva Temple |
E460686
|
entity |
| Predicate | hasSubsidiarySpires |
P133106
|
FINISHED |
| Object | urushringas |
—
|
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: urushringas | Statement: [Kandariya Mahadeva Temple, hasSubsidiarySpires, urushringas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiarySpires Context triple: [Kandariya Mahadeva Temple, hasSubsidiarySpires, urushringas]
-
A.
hasSubsidiaryPyramid
Indicates that one entity is a subsidiary or subordinate component within a larger, pyramid-structured entity.
-
B.
hasSubsidiaryTop
Indicates that one organization is the primary or top-level parent of another organization that operates as its subsidiary.
-
C.
hasSubFort
Indicates that a fort possesses or contains another, subordinate fort within its control or structure.
-
D.
hasSubTemple
Indicates that one temple includes or contains another temple as a subordinate or component temple within its structure or organization.
-
E.
hasSubsidiaryBusiness
Indicates that one business entity owns or controls another business entity as its subsidiary.
- F. None of above. chosen
Provenance (4 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99e86388190957acaaab401b5cb |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.