Triple

T23968896
Position Surface form Disambiguated ID Type / Status
Subject Mark Sway E604170 entity
Predicate fictionalUniverse P3758 FINISHED
Object The Client universe
The Client universe is the fictional legal-thriller world created by John Grisham, centered on the events and characters of his novel "The Client" and its adaptations.
E1612256 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: The Client universe | Statement: [Mark Sway, fictionalUniverse, The Client universe]
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: The Client universe
Triple: [Mark Sway, fictionalUniverse, The Client universe]
Generated description
The Client universe is the fictional legal-thriller world created by John Grisham, centered on the events and characters of his novel "The Client" and its adaptations.

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_69e29543019c8190872462e593cc50b4 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d1da2ab08190bfe653fb5a9f2c96 completed April 29, 2026, 9:39 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f7e79558c819082eb11d71d411b5b completed May 21, 2026, 9:51 p.m.
NEDg Description generation batch_6a0f7f4ce09081908de47029b8ffc097 completed May 21, 2026, 9:55 p.m.
NED2 Entity disambiguation (via description) batch_6a0f7fe7f7248190a377212661dd56b1 completed May 21, 2026, 9:58 p.m.
Created at: April 17, 2026, 9:25 p.m.