Triple
T7859852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umm al-Mu'minin |
E182467
|
entity |
| Predicate | sourceLanguageScript |
P63723
|
FINISHED |
| Object | Arabic script |
—
|
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 script | Statement: [Umm al-Mu'minin, sourceLanguageScript, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceLanguageScript Context triple: [Umm al-Mu'minin, sourceLanguageScript, Arabic script]
-
A.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
B.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
-
C.
nativeNameScript
chosen
Indicates the writing system or script in which an entity’s native name is expressed.
-
D.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
E.
originalLanguageSupport
Indicates that one entity provides or maintains functionality, content, or interaction in the original language of 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb36bb6ca4819098bc00739e07cfc8 |
completed | March 31, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:53 p.m.