Triple
T1040134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tajiks |
E22451
|
entity |
| Predicate | closelyRelatedLanguage |
P10003
|
FINISHED |
| Object | Persian |
—
|
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: Persian | Statement: [Tajiks, closelyRelatedLanguage, Persian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closelyRelatedLanguage Context triple: [Tajiks, closelyRelatedLanguage, Persian]
-
A.
linguisticallyRelatedTo
chosen
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
B.
hasNeighboringLanguages
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
-
C.
recognizedAsDistinctLanguageFrom
Indicates that one language is formally acknowledged or treated as a separate and distinct language from another, rather than as a dialect or variant of it.
-
D.
cognateOf
Indicates that two linguistic forms share a common historical origin, typically descending from the same ancestral word.
-
E.
influencedLanguage
Indicates that one language has had an effect on the development, structure, or usage of another language.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.