Triple
T35369867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Ranganathaswamy Temple, Shivanasamudra |
E1021738
|
entity |
| Predicate | positionInTriranga |
P171392
|
FINISHED |
| Object | middle Ranga |
—
|
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: middle Ranga | Statement: [Sri Ranganathaswamy Temple, Shivanasamudra, positionInTriranga, middle Ranga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTriranga Context triple: [Sri Ranganathaswamy Temple, Shivanasamudra, positionInTriranga, middle Ranga]
-
A.
positionInTrio
chosen
Indicates the specific ordered place an entity occupies within a three-member group or trio.
-
B.
positionOnTrident
Indicates that one entity occupies a specific location or slot on a trident-like structure or configuration.
-
C.
positionInTrikayaContext
Indicates the specific role or status an entity holds within the doctrinal framework of the Buddhist trikaya (three-body) concept.
-
D.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4:03 p.m.