Triple
T23822773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venkateswara |
E589281
|
entity |
| Predicate | majorTempleDistrict |
P21132
|
FINISHED |
| Object | Tirupati |
—
|
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: Tirupati | Statement: [Venkateswara, majorTempleDistrict, Tirupati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTempleDistrict Context triple: [Venkateswara, majorTempleDistrict, Tirupati]
-
A.
majorTempleLocation
chosen
Indicates that a major temple associated with an entity is located at a specified place.
-
B.
majorTempleManagingBody
Indicates that an entity serves as the primary governing or administrative body responsible for managing a major temple.
-
C.
hasTempleDistrict
Indicates that a place or settlement contains or is associated with a designated temple district area.
-
D.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
E.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7afff6c819096a0af7e008ea8d4 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.