Triple
T31897221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibn al-Sitri |
E814316
|
entity |
| Predicate | scriptSpecialization |
P184872
|
FINISHED |
| Object | naskh |
—
|
NE NERFINISHED |
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: [Ibn al-Sitri, scriptSpecialization, naskh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptSpecialization Context triple: [Ibn al-Sitri, scriptSpecialization, naskh]
-
A.
exportSpecialization
Indicates a relationship where one entity specializes in exporting particular goods, services, or resources to another entity or market.
-
B.
creatorSpecialization
Indicates the specific field, discipline, or area of expertise in which a creator primarily works or is specialized.
-
C.
branchSpecialization
Indicates that one branch or subdivision is specialized or focused in a particular area, function, or domain relative to others.
-
D.
scriptFeature
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
-
E.
parameterSpecialization
Indicates that one parameter is a more specific or constrained version of another, inheriting its role while narrowing its definition or usage.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 30, 2026, 11:59 p.m.