Triple
T19634554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsvanatha Temple, Khajuraho |
E471355
|
entity |
| Predicate | hasLanguageInInscriptions |
P15804
|
FINISHED |
| Object | Sanskrit |
—
|
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: Sanskrit | Statement: [Parsvanatha Temple, Khajuraho, hasLanguageInInscriptions, Sanskrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageInInscriptions Context triple: [Parsvanatha Temple, Khajuraho, hasLanguageInInscriptions, Sanskrit]
-
A.
inscriptionsLanguage
chosen
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
B.
officialLanguageOfInscriptions
Indicates the language officially used in the inscriptions associated with a particular entity.
-
C.
secondaryLanguageOfInscriptions
Indicates that a specified language serves as the secondary language used in the inscriptions associated with a given entity.
-
D.
hasLanguageOnPlaque
Indicates that a specific language appears in the text or inscription displayed on a particular plaque.
-
E.
hasLanguageOfArchaeologicalInterpretation
Indicates that an entity uses or is associated with a particular language in which archaeological findings or data are interpreted or described.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64104ff2881908fec49b7fba5a2e6 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.