Triple
T34193723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Venkateswara Swamy Temple, Nacharam |
E877181
|
entity |
| Predicate | locatedInVillageOrTown |
P163391
|
FINISHED |
| Object | Nacharam |
E1083213
|
NE 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: Nacharam | Statement: [Sri Venkateswara Swamy Temple, Nacharam, locatedInVillageOrTown, Nacharam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInVillageOrTown Context triple: [Sri Venkateswara Swamy Temple, Nacharam, locatedInVillageOrTown, Nacharam]
-
A.
isInVillage
Indicates that one entity is located within or belongs to the area defined as a village in relation to another entity.
-
B.
situatedInTown
chosen
Indicates that one entity is located within the geographical or administrative boundaries of a specific town.
-
C.
locatedInPlannedTown
Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
-
D.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
E.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
- F. None of above.
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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36cc83d6c88190b6c3cf4642efd533 |
completed | June 20, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.