Triple
T26959052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mallikarjuna Swamy Temple |
E678984
|
entity |
| Predicate | presidingLingamType |
P75232
|
FINISHED |
| Object | Swayambhu (self-manifested) lingam |
—
|
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: Swayambhu (self-manifested) lingam | Statement: [Mallikarjuna Swamy Temple, presidingLingamType, Swayambhu (self-manifested) lingam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presidingLingamType Context triple: [Mallikarjuna Swamy Temple, presidingLingamType, Swayambhu (self-manifested) lingam]
-
A.
lingamType
Indicates the specific type or classification of a lingam in the relationship or context being modeled.
-
B.
hasLingamType
chosen
Indicates that an entity is associated with a specific type or classification of lingam.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
E.
hasDeityPosture
Indicates the specific physical stance or pose attributed to a deity in a given context.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:29 a.m.