Triple
T8658392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ریاستجمهوری ایران |
E205481
|
entity |
| Predicate | زبان رسمی |
P236
|
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.
officialLanguage
chosen
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
B.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
C.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
D.
previousOfficialLanguage
Indicates that one language formerly held official status in a country, region, or organization before being replaced or losing that status.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc486d576081908ad28749c7971432 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.