Triple
T29529059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorani people |
E749147
|
entity |
| Predicate | dialectRelation |
P78566
|
FINISHED |
| Object | related to Torlakian 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: related to Torlakian dialects | Statement: [Gorani people, dialectRelation, related to Torlakian dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialectRelation Context triple: [Gorani people, dialectRelation, related to Torlakian dialects]
-
A.
dialectDocumentation
Indicates that there exists documentation or descriptive information specifically about a particular dialect or dialectal variety.
-
B.
relatedDialect
chosen
Indicates that one dialect has a recognized linguistic relationship or close affinity to another dialect.
-
C.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
D.
dialectFamily
Indicates that one dialect belongs to, or is classified under, a particular dialect family.
-
E.
hasDialectalDifferenceWith
Indicates that two language varieties differ from each other in dialectal features such as pronunciation, vocabulary, or grammar.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c9efdfc8190b2137dc6e1685baf |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:50 p.m.