Triple
T34424783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udupi Sri Krishna Temple |
E883637
|
entity |
| Predicate | numberOfAshtaMathas |
P205431
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Udupi Sri Krishna Temple, numberOfAshtaMathas, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAshtaMathas Context triple: [Udupi Sri Krishna Temple, numberOfAshtaMathas, 8]
-
A.
numberOfSutras
Indicates the quantity or count of sutras associated with a given entity.
-
B.
definesNumberOfTattvas
Indicates that an entity specifies or establishes the total count of tattvas (fundamental principles or elements) in a given system.
-
C.
numberOfSkandhas
Indicates the relationship that specifies how many skandhas (aggregates) are associated with a given entity or concept.
-
D.
associatedSampradaya
Indicates a relationship where one entity is linked or connected to a particular sampradaya (spiritual or religious tradition/lineage) with which it is affiliated or identified.
-
E.
numberOfPadarthas
Indicates the relationship that specifies how many distinct padarthas (categories or entities) are associated with or contained in a given subject.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2 a.m.