Triple
T8790698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venyovsky Uyezd |
E209155
|
entity |
| Predicate | sovereignAtTheTime |
P40954
|
FINISHED |
| Object | Emperor of Russia |
—
|
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: Emperor of Russia | Statement: [Venyovsky Uyezd, sovereignAtTheTime, Emperor of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereignAtTheTime Context triple: [Venyovsky Uyezd, sovereignAtTheTime, Emperor of Russia]
-
A.
sovereignAtTime
chosen
Indicates that an entity holds sovereign authority or ruling power over another entity during a specified time or time interval.
-
B.
sovereignStateUntil
Indicates that an entity functioned as a sovereign state up to a specified end time or date.
-
C.
sovereigntyFormedBy
Indicates that a sovereignty or governing authority comes into existence through the actions, decisions, or processes of a specified agent or mechanism.
-
D.
sovereignStateDuring
Indicates that one entity functioned as the sovereign state governing another entity during a specified time period.
-
E.
sovereignClaimedBy
Indicates that a territory or entity is asserted to be under the sovereignty or ultimate authority of a particular claimant.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8d25f881908863d636fa57a8a2 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.