Triple
T32893538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zalesye |
E841402
|
entity |
| Predicate | laterPoliticalSuccessor |
P49035
|
FINISHED |
| Object | Grand Duchy of Moscow |
—
|
NE NERFINISHED |
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: Grand Duchy of Moscow | Statement: [Zalesye, laterPoliticalSuccessor, Grand Duchy of Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPoliticalSuccessor Context triple: [Zalesye, laterPoliticalSuccessor, Grand Duchy of Moscow]
-
A.
laterAdministrativeSuccessor
chosen
Indicates that one administrative entity succeeds another in governing authority or jurisdiction at a later time.
-
B.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
C.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
D.
successorSovereign
Indicates that one entity becomes the next ruling sovereign following another entity, inheriting their position of supreme authority.
-
E.
deFactoSuccessor
Indicates that one entity has effectively taken over the role, function, or position of another, even if not formally or legally recognized as its successor.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: May 1, 2026, 1:18 a.m.