Triple
T8864807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Ali Ibn Muqla |
E210989
|
entity |
| Predicate | scriptTypeWorkedOn |
P85066
|
FINISHED |
| Object | naskh |
—
|
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: naskh | Statement: [Abu Ali Ibn Muqla, scriptTypeWorkedOn, naskh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptTypeWorkedOn Context triple: [Abu Ali Ibn Muqla, scriptTypeWorkedOn, naskh]
-
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.
workTypeContributedTo
Indicates that an entity contributed to the creation, development, or production of a particular type of work.
-
C.
scriptDevelopedFor
Indicates that a script was specifically created or developed for use by, or in the context of, a particular entity or purpose.
-
D.
worksOnProgram
Indicates that an entity is actively involved in contributing effort or performing tasks on a particular program.
-
E.
scriptCategory
Indicates the classification or type of script to which an entity (such as a written work, code, or performance text) belongs.
- F. None of above. chosen
Provenance (4 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc610569d08190b108107dfe397f18 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:51 p.m.