Triple
T28588758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaralingeswara Swamy Temple |
E723581
|
entity |
| Predicate | hasSacredLingam |
P80427
|
FINISHED |
| Object | Amaralingeswara lingam |
—
|
NE NERFINISHED |
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: Amaralingeswara lingam | Statement: [Amaralingeswara Swamy Temple, hasSacredLingam, Amaralingeswara lingam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredLingam Context triple: [Amaralingeswara Swamy Temple, hasSacredLingam, Amaralingeswara lingam]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasSacredImage
Indicates that one entity possesses or is associated with an image regarded as sacred or religiously significant.
-
C.
hasSacredWeapon
Indicates that an entity possesses or is associated with a weapon regarded as holy, consecrated, or religiously significant.
-
D.
hasLinga
chosen
Indicates a relationship where an entity possesses or is associated with a linga (a symbolic representation, typically of Shiva).
-
E.
hasSacredNumber
Indicates that a particular number is regarded as sacred, holy, or spiritually significant in relation to an 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 4:19 a.m.