Triple
T311837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naskh script |
E7624
|
entity |
| Predicate | writingSystemUser |
P454
|
FINISHED |
| Object | Arabic-speaking communities |
—
|
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: Arabic-speaking communities | Statement: [Naskh script, writingSystemUser, Arabic-speaking communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemUser Context triple: [Naskh script, writingSystemUser, Arabic-speaking communities]
-
A.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
writingSystemStatus
Indicates the current functional or sociolinguistic state of a writing system, such as whether it is actively used, obsolete, official, or endangered.
-
C.
writingSystemClass
Indicates that one entity is classified as a type or category of writing system to which the other entity belongs.
-
D.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of another entity.
-
E.
rite
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea49636c8190a69cbd951fc0a4db |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.