Triple
T25553858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veera Ballala II |
E640513
|
entity |
| Predicate | issuedInscriptionsIn |
P160124
|
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: [Veera Ballala II, issuedInscriptionsIn, Sanskrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedInscriptionsIn Context triple: [Veera Ballala II, issuedInscriptionsIn, Sanskrit]
-
A.
issuedInscription
Indicates that an authority or source formally created and released a specific inscription or written record.
-
B.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
C.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
D.
numberOfInscriptions
Indicates the total count of inscriptions associated with a given entity or object.
-
E.
inscribedOn
Indicates that text, symbols, or markings are written or carved onto the surface of an object.
- F. None of above. chosen
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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 21, 2026, 3:38 p.m.