Triple
T2152446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Syriac script |
E47809
|
entity |
| Predicate | hasDiacriticsFor |
P2270
|
FINISHED |
| Object | vowel indication |
—
|
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: vowel indication | Statement: [East Syriac script, hasDiacriticsFor, vowel indication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiacriticsFor Context triple: [East Syriac script, hasDiacriticsFor, vowel indication]
-
A.
usesDiacritics
chosen
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
B.
diacriticType
Indicates the specific kind or category of diacritic mark associated with a character or symbol.
-
C.
hasAccent
Indicates that an entity speaks with or possesses a particular accent or distinctive pronunciation style.
-
D.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
-
E.
hasCombiningMarks
Indicates that an entity (such as a character or string) includes one or more combining marks attached to a base element.
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe48ad148190a7d6cc88fd38a660 |
completed | March 7, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.