Triple
T31857471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalaj language |
E813235
|
entity |
| Predicate | sometimesMisclassifiedAs |
P14654
|
FINISHED |
| Object | Azerbaijani dialect |
—
|
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: Azerbaijani dialect | Statement: [Khalaj language, sometimesMisclassifiedAs, Azerbaijani dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesMisclassifiedAs Context triple: [Khalaj language, sometimesMisclassifiedAs, Azerbaijani dialect]
-
A.
canMisclassify
Indicates that one entity has the potential or ability to incorrectly classify or label another entity.
-
B.
isSometimesClassifiedAs
chosen
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
-
C.
misidentifiedAs
Indicates that one entity has been incorrectly recognized, labeled, or understood as another, distinct entity.
-
D.
usuallyClassifiedAs
Indicates that an entity is most commonly or typically placed into a particular category or type, though other classifications may also exist.
-
E.
notClassifiedAs
Indicates that an entity is explicitly not assigned to, or excluded from, a particular class or category.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b06b872481908372becd54a1792e |
completed | May 3, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:52 p.m.