Triple
T1918659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorani |
E40075
|
entity |
| Predicate | primaryStatusIn |
P29579
|
FINISHED |
| Object | one of main written standards of Kurdish |
—
|
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: one of main written standards of Kurdish | Statement: [Sorani, primaryStatusIn, one of main written standards of Kurdish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStatusIn Context triple: [Sorani, primaryStatusIn, one of main written standards of Kurdish]
-
A.
primaryStatus
chosen
Indicates the main or most important status assigned to an entity among potentially multiple statuses.
-
B.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
C.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
D.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
-
E.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb211eda88190865de7a0522a453d |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.