Triple
T633070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerbaijani language |
E15962
|
entity |
| Predicate | currentOfficialScriptInIran |
P454
|
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: [Azerbaijani language, currentOfficialScriptInIran, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOfficialScriptInIran Context triple: [Azerbaijani language, currentOfficialScriptInIran, Arabic script]
-
A.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
B.
isMostWidelyUsedWritingSystem
Indicates that the subject writing system is used by more people or in more contexts than any other writing system.
-
C.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
D.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
E.
hasOfficialOrthography
Indicates that an entity has a formally recognized and standardized system for writing its language or name.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec3b6488190aa0dce216c089a2e |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.