Triple
T38379050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manghit clan |
E893705
|
entity |
| Predicate | statusAfterRussianConquest |
P39754
|
FINISHED |
| Object | protectorate of the Russian Empire |
—
|
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: protectorate of the Russian Empire | Statement: [Manghit clan, statusAfterRussianConquest, protectorate of the Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterRussianConquest Context triple: [Manghit clan, statusAfterRussianConquest, protectorate of the Russian Empire]
-
A.
statusInRussianEmpire
chosen
Indicates the legal or social standing an entity held within the political and administrative system of the Russian Empire.
-
B.
countryDuringTsardom
Indicates that an entity functioned as a country or political unit during the historical period of tsardom.
-
C.
joinedRussianEmpire
Indicates that an entity became part of, or was incorporated into, the Russian Empire.
-
D.
tsarRussia
Indicates that the subject is the tsar (monarch) who rules over Russia.
-
E.
countryDuringRussianEmpirePeriod
Indicates that a given country existed or is considered in the context of the historical period of the Russian Empire.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 3, 2026, 4:31 p.m.