Triple
T23607715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumzari people |
E582941
|
entity |
| Predicate | historicalInfluenceOnLanguage |
P55689
|
FINISHED |
| Object | Persian |
—
|
NE NERFINISHED |
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: [Kumzari people, historicalInfluenceOnLanguage, Persian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalInfluenceOnLanguage Context triple: [Kumzari people, historicalInfluenceOnLanguage, Persian]
-
A.
historicalLanguageInfluenceOn
chosen
Indicates that one language has had a shaping or contributory effect on the development, vocabulary, structure, or usage of another language over time.
-
B.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
C.
languageInfluence
Indicates that one language has an effect on the development, usage, or characteristics of another language.
-
D.
linguisticInfluence
Indicates that one entity has affected, shaped, or contributed to the language, style, or linguistic features of another entity.
-
E.
roleInLanguageHistory
Indicates the specific function, influence, or contribution an entity has had within the historical development or evolution of a 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0f107048190b81eade6a50db2da |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:44 p.m.