Triple
T14491151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shikhara |
E359364
|
entity |
| Predicate | roleInTemplePlan |
P51530
|
FINISHED |
| Object | vertical axis |
—
|
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: vertical axis | Statement: [Shikhara, roleInTemplePlan, vertical axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTemplePlan Context triple: [Shikhara, roleInTemplePlan, vertical axis]
-
A.
roleAtTemple
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
-
B.
positionInTemple
chosen
Indicates the specific location or role an entity occupies within a temple.
-
C.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
D.
roleInShinto
Indicates that an entity holds a particular function, status, or significance within the context of Shinto beliefs, practices, or institutions.
-
E.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930d820481908b9813014dd02540 |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.