Triple
T14512471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الخَابُور |
E340430
|
entity |
| Predicate | يُكتب_بالأبجدية |
P95800
|
FINISHED |
| Object | الأبجدية العربية |
—
|
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: الأبجدية العربية | Statement: [الخَابُور, يُكتب_بالأبجدية, الأبجدية العربية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يُكتب_بالأبجدية Context triple: [الخَابُور, يُكتب_بالأبجدية, الأبجدية العربية]
-
A.
isWrittenWith
chosen
Indicates that something is created or expressed using a particular writing tool, medium, or system.
-
B.
דיני כתיבה בו
Indicates that the subject is governed by the same halachic laws and requirements of writing that apply to it (e.g., that the laws of writing are operative in this context).
-
C.
alphabetic
Indicates that the characters in a string or sequence consist solely of letters from an alphabet, with no digits or special symbols.
-
D.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
E.
alphabet
Indicates that one entity is an alphabet or set of symbols used for representing elements (such as characters or tokens) in relation to 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6c6054819086b4c0ce1d83fdc5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.