Triple
T19986173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swamimalai Murugan Temple |
E493936
|
entity |
| Predicate | numberOfSacredSteps |
P138211
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Swamimalai Murugan Temple, numberOfSacredSteps, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSacredSteps Context triple: [Swamimalai Murugan Temple, numberOfSacredSteps, 60]
-
A.
numberOfStepsSymbolism
Indicates the symbolic or thematic meaning associated with a specific number of steps in a sequence, process, or structure.
-
B.
hasStepsToTemple
Indicates that one place or structure includes or provides a set of steps leading to a temple.
-
C.
sacredDirection
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural context.
-
D.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
E.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d16f60c81909ba02c0a3429ecae |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:29 p.m.