Triple
T29635134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conquest of Astrakhan (1556) |
E755689
|
entity |
| Predicate | underTheRuleOf |
P87031
|
FINISHED |
| Object | Ivan IV of Russia |
—
|
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: Ivan IV of Russia | Statement: [Conquest of Astrakhan (1556), underTheRuleOf, Ivan IV of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underTheRuleOf Context triple: [Conquest of Astrakhan (1556), underTheRuleOf, Ivan IV of Russia]
-
A.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
B.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
C.
laterUnderRuleOf
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
-
D.
designedUnderRuleOf
Indicates that something was designed or created while a particular authority, regime, or set of rules was in power or in effect.
-
E.
underTheReignOf
chosen
Indicates that one entity existed or operated during the period when another entity (typically a ruler or authority) held power or governance.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 28, 2026, 6:43 p.m.