Triple
T32133753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parbatiya |
E820716
|
entity |
| Predicate | traditionalScriptForLanguage |
P16462
|
FINISHED |
| Object | Devanagari script |
—
|
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: Devanagari script | Statement: [Parbatiya, traditionalScriptForLanguage, Devanagari script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalScriptForLanguage Context triple: [Parbatiya, traditionalScriptForLanguage, Devanagari script]
-
A.
associatedLanguageScript
chosen
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
B.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
-
C.
nativeNameScript
Indicates the writing system or script in which an entity’s native name is expressed.
-
D.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
-
E.
textScript
Indicates the writing system or script in which a given piece of text is expressed.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 12:30 a.m.