Triple
T27112535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siladitya V |
E686752
|
entity |
| Predicate | usesScriptInInscriptions |
P22774
|
FINISHED |
| Object | Brahmi-derived scripts |
—
|
NE NERFINISHED |
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: Brahmi-derived scripts | Statement: [Siladitya V, usesScriptInInscriptions, Brahmi-derived scripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptInInscriptions Context triple: [Siladitya V, usesScriptInInscriptions, Brahmi-derived scripts]
-
A.
usesScriptFor
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
B.
usedScriptOnStamps
Indicates that a particular writing system or script was employed on the text or inscriptions appearing on stamps.
-
C.
scriptOfInscription
chosen
Indicates the writing system or script in which a given inscription is written.
-
D.
usedInScripts
Indicates that something (such as a tool, method, or resource) is employed or referenced within one or more scripts.
-
E.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 8:54 a.m.