Triple
T37680446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taraknath |
E938213
|
entity |
| Predicate | typicalScriptInDevanagari |
P199100
|
FINISHED |
| Object | तारणाथ |
E938213
|
NE 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: तारणाथ | Statement: [Taraknath, typicalScriptInDevanagari, तारणाथ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScriptInDevanagari Context triple: [Taraknath, typicalScriptInDevanagari, तारणाथ]
-
A.
nameInDevanagari
Indicates that an entity’s name is written or represented using the Devanagari script.
-
B.
typicalScriptInOriginLanguage
chosen
Indicates that an entity (such as a work or text) is typically written or presented in its original language’s standard script.
-
C.
scriptForSikhReligiousTexts
Indicates the script or writing system used to write Sikh religious texts.
-
D.
textScript
Indicates the writing system or script in which a given piece of text is expressed.
-
E.
usesChatusrutiRishabha
Indicates that one entity employs or incorporates the Chatusruti Rishabha (a specific swara/scale degree) in relation to another entity, such as in a musical composition, scale, or performance.
- F. None of above.
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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40d66e49c881908116a1a47f5730b5 |
completed | June 28, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.