Triple
T2489567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cossacks |
E52005
|
entity |
| Predicate | statusInRussianEmpire |
P39754
|
FINISHED |
| Object | privileged military estate |
—
|
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: privileged military estate | Statement: [Cossacks, statusInRussianEmpire, privileged military estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInRussianEmpire Context triple: [Cossacks, statusInRussianEmpire, privileged military estate]
-
A.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
B.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
-
C.
joinedRussianEmpire
Indicates that an entity became part of, or was incorporated into, the Russian Empire.
-
D.
wasProtectorateOf
Indicates that one entity was formerly under the protection and partial control of another, typically more powerful, entity.
-
E.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd17b7a048190bcc8f0a66514a052 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1318f7881908a8fc42943df4879 |
completed | March 7, 2026, 7:18 a.m. |
Created at: March 6, 2026, 9:45 p.m.