Triple
T29835599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rurikid principalities |
E757648
|
entity |
| Predicate | legacyFor |
P122614
|
FINISHED |
| Object | Russian statehood |
—
|
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: Russian statehood | Statement: [Rurikid principalities, legacyFor, Russian statehood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legacyFor Context triple: [Rurikid principalities, legacyFor, Russian statehood]
-
A.
heritageFor
chosen
Indicates that something serves as a source, basis, or contributing legacy for another entity’s heritage or tradition.
-
B.
usesLegacyOf
Indicates that one entity makes use of, builds upon, or derives benefit from the historical work, reputation, or established influence of another entity.
-
C.
managedLegacyOf
Indicates that one entity was responsible for overseeing, preserving, or directing the continuation and impact of another entity’s legacy.
-
D.
legacyPlan
Indicates that an entity is associated with or governed by an older, previously existing plan rather than a current or updated one.
-
E.
heritageSuccessor
Indicates that one entity is the successor or inheritor of another in terms of heritage, lineage, or cultural tradition.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67605e9548190855ca2d77608b4dc |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:36 p.m.