Triple
T946229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashmiri Pandit |
E20418
|
entity |
| Predicate | scriptCurrentlyUsed |
P9329
|
FINISHED |
| Object | Devanagari |
—
|
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 | Statement: [Kashmiri Pandit, scriptCurrentlyUsed, Devanagari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCurrentlyUsed Context triple: [Kashmiri Pandit, scriptCurrentlyUsed, Devanagari]
-
A.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
B.
scriptCode
chosen
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
C.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
D.
scriptSystem
Indicates that one entity is the scripting or programming system used to control, configure, or automate the behavior of another entity.
-
E.
scriptOnFlag
Indicates that a script is attached to and/or executed when a specific flag or condition is set.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a61b648190b1b6c932e047e161 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29f05f481908814bd11f235e9d0 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.