Triple
T22569385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meitei Mayek script |
E558038
|
entity |
| Predicate | scriptTypeFeature |
P51137
|
FINISHED |
| Object | inherent vowel in consonant letters |
—
|
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: inherent vowel in consonant letters | Statement: [Meitei Mayek script, scriptTypeFeature, inherent vowel in consonant letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptTypeFeature Context triple: [Meitei Mayek script, scriptTypeFeature, inherent vowel in consonant letters]
-
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.
scriptFeature
chosen
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
-
C.
scriptSupport
Indicates that one entity provides or enables scripting capabilities or support for another entity.
-
D.
scriptSource
Indicates that one entity is the origin or provider of the script used or referenced by another entity.
-
E.
scriptVariantLanguage
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fac7db08190ba4660535571498d |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:52 p.m.