Triple

T24907727
Position Surface form Disambiguated ID Type / Status
Subject The Eyre Affair E623759 entity
Predicate mainCharacter P1183 FINISHED
Object Thursday Next
Thursday Next is a literary detective in an alternate-history Britain who polices the boundaries between fiction and reality in Jasper Fforde’s comic fantasy series.
E1655791 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: Thursday Next | Statement: [The Eyre Affair, mainCharacter, Thursday Next]
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: Thursday Next
Triple: [The Eyre Affair, mainCharacter, Thursday Next]
Generated description
Thursday Next is a literary detective in an alternate-history Britain who polices the boundaries between fiction and reality in Jasper Fforde’s comic fantasy series.

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_69e2fac797cc8190b30d77f4121099ac completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f4236c86c08190ae6b0c8738febe69 completed May 1, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a103329f5608190b26d4489ea3a34a2 completed May 22, 2026, 10:42 a.m.
NEDg Description generation batch_6a1033ece8248190bc0ee7fa4976848d completed May 22, 2026, 10:46 a.m.
NED2 Entity disambiguation (via description) batch_6a10348fb55c819087a28d4a7280589c completed May 22, 2026, 10:48 a.m.
Created at: April 18, 2026, 5:27 a.m.