Triple

T33530030
Position Surface form Disambiguated ID Type / Status
Subject Principality of Kostroma E858749 entity
Predicate hasTitleHolder P1911 FINISHED
Object Kostroma prince
A Kostroma prince was a medieval Russian noble ruler associated with the Principality of Kostroma, one of the historical principalities of northeastern Rus'.
E2055057 NE 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: Kostroma prince | Statement: [Principality of Kostroma, hasTitleHolder, Kostroma prince]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kostroma prince
Triple: [Principality of Kostroma, hasTitleHolder, Kostroma prince]
Generated description
A Kostroma prince was a medieval Russian noble ruler associated with the Principality of Kostroma, one of the historical principalities of northeastern Rus'.

Provenance (5 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_69f34978caf4819083f90eba4944d8e8 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f6a4a0988190b314f9362f18e455 completed May 3, 2026, 7:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a35a67ec2188190ba3f57e2fa763c48 completed June 19, 2026, 8:28 p.m.
NEDg Description generation batch_6a35a74280e481908a5e8d58159ccf14 completed June 19, 2026, 8:32 p.m.
NED2 Entity disambiguation (via description) batch_6a35a7da68bc819090b95df78ec28e57 completed June 19, 2026, 8:34 p.m.
Created at: May 1, 2026, 1:39 a.m.