Triple
T36313397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palampet village |
E894121
|
entity |
| Predicate | religiousSiteTypeNearby |
P29505
|
FINISHED |
| Object | Hindu temple |
—
|
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: Hindu temple | Statement: [Palampet village, religiousSiteTypeNearby, Hindu temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousSiteTypeNearby Context triple: [Palampet village, religiousSiteTypeNearby, Hindu temple]
-
A.
nearReligiousSite
chosen
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
B.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
C.
religiousTextAssociationNearby
Indicates a spatial relationship where a religious text or related object is located close to or in the immediate vicinity of another entity.
-
D.
heritageSiteTypeNearby
Indicates that a particular type of heritage site is located in close proximity to the referenced entity.
-
E.
religiousSiteInRegion
Indicates that a religious site is located within or belongs to a specified geographic region.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: May 3, 2026, 4:09 p.m.