Triple

T30123501
Position Surface form Disambiguated ID Type / Status
Subject Laskaris family E765621 entity
Predicate hasMember P10 FINISHED
Object Nikephoros Laskaris
Nikephoros Laskaris was a member of the prominent Byzantine Laskaris family, known for producing emperors and high-ranking nobles in the late Byzantine period.
E1974848 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: Nikephoros Laskaris | Statement: [Laskaris family, hasMember, Nikephoros Laskaris]
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: Nikephoros Laskaris
Triple: [Laskaris family, hasMember, Nikephoros Laskaris]
Generated description
Nikephoros Laskaris was a member of the prominent Byzantine Laskaris family, known for producing emperors and high-ranking nobles in the late Byzantine period.

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_69f2247716748190ae4f16998f49ddf1 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67deccfe08190963db977b17c8ab4 completed May 2, 2026, 10:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2b848b13c8819084bfcbdceeb7c02b completed June 12, 2026, 4:01 a.m.
NEDg Description generation batch_6a2b8a5a348c8190a74f46dde8c09f99 completed June 12, 2026, 4:26 a.m.
NED2 Entity disambiguation (via description) batch_6a2b8f3ae3dc8190bb085871d208be43 completed June 12, 2026, 4:46 a.m.
Created at: April 29, 2026, 7:13 p.m.