Triple
T3292422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rurik |
E69130
|
entity |
| Predicate | roleInPrimaryChronicle |
P28173
|
FINISHED |
| Object | invited ruler of the Rus' |
—
|
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: invited ruler of the Rus' | Statement: [Rurik, roleInPrimaryChronicle, invited ruler of the Rus']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPrimaryChronicle Context triple: [Rurik, roleInPrimaryChronicle, invited ruler of the Rus']
-
A.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
B.
Chronica_subject
chosen
Indicates that an entity serves as the subject or main focus of a chronicle, record, or historical account.
-
C.
chronicledBy
Indicates that something is documented, recorded, or described in detail by a particular source, author, or record.
-
D.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
E.
narratorRole
Indicates that one entity serves as the narrator of another entity (such as a story, text, or media work), specifying the narrative role or function it performs.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb07379dc8190b7bb409bcf42bdd6 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.