Triple
T11431692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nandi |
E270898
|
entity |
| Predicate | hasShrinePosition |
P67014
|
FINISHED |
| Object | in front of the main sanctum of Shiva |
—
|
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: in front of the main sanctum of Shiva | Statement: [Nandi, hasShrinePosition, in front of the main sanctum of Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShrinePosition Context triple: [Nandi, hasShrinePosition, in front of the main sanctum of Shiva]
-
A.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
B.
hasInnerShrine
Indicates that one entity contains or includes another entity that functions as an inner shrine within it.
-
C.
hasAltarLocation
chosen
Indicates that an altar is situated at or associated with a specific location.
-
D.
hasShrineTitle
Indicates that an entity holds or is associated with a specific honorific or formal title used in the context of a shrine.
-
E.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c30d788190b0c939b33de89277 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.