Triple
T26137474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feyli |
E659420
|
entity |
| Predicate | hasPhonologicalSimilarity |
P8038
|
FINISHED |
| Object | other Southern Kurdish dialects |
—
|
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: other Southern Kurdish dialects | Statement: [Feyli, hasPhonologicalSimilarity, other Southern Kurdish dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhonologicalSimilarity Context triple: [Feyli, hasPhonologicalSimilarity, other Southern Kurdish dialects]
-
A.
hasPhonologicalSimilarityTo
chosen
Indicates that two linguistic elements share similar sound patterns or phonological features.
-
B.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
C.
hasGrammaticalSimilarityTo
Indicates that two linguistic elements share similar grammatical structure, form, or function.
-
D.
hasHomophones
Indicates that two or more linguistic expressions share the same pronunciation but differ in meaning, spelling, or both.
-
E.
hasLexicalSimilarityWith
Indicates that two linguistic items share a significant degree of similarity in form, structure, or wording.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:18 p.m.