Triple
T11860994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virūḍhaka |
E282155
|
entity |
| Predicate | templePlacement |
P51530
|
FINISHED |
| Object | southern side of temple gates |
—
|
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: southern side of temple gates | Statement: [Virūḍhaka, templePlacement, southern side of temple gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templePlacement Context triple: [Virūḍhaka, templePlacement, southern side of temple gates]
-
A.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
B.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
C.
positionInTemple
chosen
Indicates the specific location or role an entity occupies within a temple.
-
D.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.