Triple

T31965453
Position Surface form Disambiguated ID Type / Status
Subject Flandry series E816161 entity
Predicate hasBook P29317 FINISHED
Object Flandry’s Legacy
Flandry’s Legacy is a science fiction novel by Poul Anderson set in his Technic History universe, following the exploits and legacy of the Terran Empire agent Dominic Flandry.
E816155 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: Flandry’s Legacy | Statement: [Flandry series, hasBook, Flandry’s Legacy]
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: Flandry’s Legacy
Triple: [Flandry series, hasBook, Flandry’s Legacy]
Generated description
Flandry’s Legacy is a science fiction novel by Poul Anderson set in his Technic History universe, following the exploits and legacy of the Terran Empire agent Dominic Flandry.

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_69f348f5ae5481909da0247869f51955 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b2e9f9f48190b52e9381133c102d completed May 3, 2026, 2:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2ed4dada64819094d8b1b5ac49a0f9 completed June 14, 2026, 4:20 p.m.
NEDg Description generation batch_6a2ed5c07e34819098385a0d7a928fa4 completed June 14, 2026, 4:24 p.m.
NED2 Entity disambiguation (via description) batch_6a2ed7379d088190b7481d5c7eb61b9f completed June 14, 2026, 4:30 p.m.
Created at: May 1, 2026, 12:09 a.m.