Triple
T7073496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swamimalai |
E164755
|
entity |
| Predicate | templeTank |
P46303
|
FINISHED |
| Object | Swami Pushkarani |
—
|
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: Swami Pushkarani | Statement: [Swamimalai, templeTank, Swami Pushkarani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeTank Context triple: [Swamimalai, templeTank, Swami Pushkarani]
-
A.
hasTempleTank
chosen
Indicates that a temple includes or is associated with a specific water tank or reservoir used for religious or ritual purposes.
-
B.
sacredTankName
Indicates that an entity has a name identifying it as a sacred or holy water tank or reservoir.
-
C.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
E.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4cb76548190bd98876f8ba925b7 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.