Triple
T18534187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirumala Venkateswara Temple |
E452918
|
entity |
| Predicate | notableQueueSystem |
P668
|
FINISHED |
| Object | Sarva Darshan |
—
|
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: Sarva Darshan | Statement: [Tirumala Venkateswara Temple, notableQueueSystem, Sarva Darshan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableQueueSystem Context triple: [Tirumala Venkateswara Temple, notableQueueSystem, Sarva Darshan]
-
A.
notableWorker
Indicates that the subject is a worker who is distinguished or recognized for being particularly important, prominent, or exemplary in their work.
-
B.
notableSystem
chosen
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
C.
notableProcess
Indicates that an entity is associated with a process, procedure, or operation that is particularly significant, prominent, or noteworthy in some context.
-
D.
notablePackage
Indicates that an entity is a particularly significant, well-known, or otherwise noteworthy package within its domain.
-
E.
notableDeployment
Indicates that an entity has been deployed or launched in a way that is particularly significant, prominent, or widely recognized.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53400d548819080b17f30b3ee7174 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.