Triple
T32919919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Андрей Александрович |
E842114
|
entity |
| Predicate | принадлежностьКДинастии |
P91745
|
FINISHED |
| Object | Рюриковичи |
—
|
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: Рюриковичи | Statement: [Андрей Александрович, принадлежностьКДинастии, Рюриковичи]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: принадлежностьКДинастии Context triple: [Андрей Александрович, принадлежностьКДинастии, Рюриковичи]
-
A.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
B.
partOfDynasty
chosen
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
C.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
-
D.
basedOnDynasty
Indicates that something is derived from, influenced by, or established on the foundation of a particular dynasty.
-
E.
associatedWithDynastyOrFaction
Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d0d604e88190ad06268f76137168 |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.