Triple
T29351060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Kurdish |
E744313
|
entity |
| Predicate | hasLatinAlphabetStandard |
P193475
|
FINISHED |
| Object | Hawar alphabet |
—
|
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: Hawar alphabet | Statement: [Northern Kurdish, hasLatinAlphabetStandard, Hawar alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatinAlphabetStandard Context triple: [Northern Kurdish, hasLatinAlphabetStandard, Hawar alphabet]
-
A.
usesLatinAlphabetSince
Indicates that an entity has employed the Latin alphabet as its writing system starting from a specific point in time and continuing thereafter.
-
B.
hasLatinText
Indicates that an entity possesses or is associated with text written in Latin.
-
C.
hasUnicodeStandard
Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
-
D.
hasRomanizationStandard
Indicates that an entity’s romanized form follows a specified romanization standard or system.
-
E.
hasLatinizedName
Indicates that an entity is associated with a version of its name that has been converted into Latin form or spelling.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: April 28, 2026, 2:06 p.m.