Triple
T2152466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Syriac script |
E47809
|
entity |
| Predicate | hasLetterForms |
P9189
|
FINISHED |
| Object | initial |
—
|
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: initial | Statement: [East Syriac script, hasLetterForms, initial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLetterForms Context triple: [East Syriac script, hasLetterForms, initial]
-
A.
hasContextualLetterForms
chosen
Indicates that the written form of a letter changes shape depending on its surrounding characters or position within a word.
-
B.
hasThreeLetterForm
Indicates that an entity’s written or symbolic form consists of exactly three letters.
-
C.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
D.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
E.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
- 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.