Triple
T21767246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian Cossack Brigade |
E537325
|
entity |
| Predicate | laterLanguageOfCommand |
P145876
|
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: [Persian Cossack Brigade, laterLanguageOfCommand, Persian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLanguageOfCommand Context triple: [Persian Cossack Brigade, laterLanguageOfCommand, Persian]
-
A.
languageOfCommand
Indicates that a specified language is the one in which a given command is expressed or issued.
-
B.
suffixLanguage
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
-
C.
possibleLanguage
Indicates that an entity could plausibly be expressed, interpreted, or communicated in a given language.
-
D.
laterOfficialLanguage
Indicates that one language became an official language of an entity at a later time than another language.
-
E.
laterLanguageDominant
Indicates that one language becomes the dominant or primary language for an entity at a later point in time, after another language previously held that role.
- F. None of above. chosen
Provenance (4 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031ab57808190b9af6d8f0ead1051 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.