Triple
T30438340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zemshchina |
E774371
|
entity |
| Predicate | reasonForDivision |
P19352
|
FINISHED |
| Object | political control by Ivan IV |
—
|
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: political control by Ivan IV | Statement: [Zemshchina, reasonForDivision, political control by Ivan IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDivision Context triple: [Zemshchina, reasonForDivision, political control by Ivan IV]
-
A.
reasonForSplit
chosen
Indicates the cause, motivation, or circumstance that led to a separation or breakup between entities.
-
B.
divorceReason
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
-
C.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
D.
diversionReason
Indicates the reason or cause for redirecting or changing the original route, plan, or course of action.
-
E.
divisionRenamedFrom
Indicates that a division currently known by one name was previously known by another specified name.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 29, 2026, 8:08 p.m.