Triple
T16964183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulu script |
E411501
|
entity |
| Predicate | scriptUsageChange |
P125402
|
FINISHED |
| Object | largely replaced by Kannada script for Tulu |
—
|
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: largely replaced by Kannada script for Tulu | Statement: [Tulu script, scriptUsageChange, largely replaced by Kannada script for Tulu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptUsageChange Context triple: [Tulu script, scriptUsageChange, largely replaced by Kannada script for Tulu]
-
A.
scriptUsagePeriod
Indicates the time span during which a particular script is or was actively used or valid.
-
B.
scriptUsedCurrently
Indicates that a particular writing system or script is the one presently in use for a given language, text, or context.
-
C.
scriptChangePolicy
Indicates a policy governing when, how, or under what conditions a script may be modified or updated.
-
D.
scriptAdaptationFrom
Indicates that a script is adapted or derived from a pre-existing source work (such as a book, play, or earlier script).
-
E.
scriptUsedForLanguage
Indicates that a particular writing script is employed to write or represent a given language.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a2cda88190bd574a869f0e43e9 |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.