Triple
T31399317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | واسی |
E800949
|
entity |
| Predicate | تعلق_دارد_به_خانواده_زبانها |
P99455
|
FINISHED |
| Object | خانواده زبانهای هندوایرانی |
—
|
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: خانواده زبانهای هندوایرانی | Statement: [واسی, تعلق_دارد_به_خانواده_زبانها, خانواده زبانهای هندوایرانی]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: تعلق_دارد_به_خانواده_زبانها Context triple: [واسی, تعلق_دارد_به_خانواده_زبانها, خانواده زبانهای هندوایرانی]
-
A.
languageFamilyRelation
chosen
Indicates a relationship where one language belongs to, descends from, or is otherwise classified within a particular language family.
-
B.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
C.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
D.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
-
E.
coversLanguageFamily
Indicates that one entity includes or encompasses a particular language family within its scope or subject matter.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.