Triple
T8710247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaddare script |
E206755
|
entity |
| Predicate | writingMediums |
P48838
|
FINISHED |
| Object | handwritten documents |
—
|
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: handwritten documents | Statement: [Kaddare script, writingMediums, handwritten documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingMediums Context triple: [Kaddare script, writingMediums, handwritten documents]
-
A.
manuscriptMedium
chosen
Indicates the material or physical medium on which a manuscript is written or produced.
-
B.
writingMediumModern
Indicates that the writing activity is carried out using a modern medium or tool (such as digital or contemporary writing instruments) rather than traditional ones.
-
C.
fictionalMedium
Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
-
D.
written
Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3034708190b895eaf890d62198 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.