Triple
T33738922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Harvey |
E864505
|
entity |
| Predicate | wroteNovel |
P2831
|
FINISHED |
| Object |
All She Wants
All She Wants is a novel by British writer Jonathan Harvey, known for its sharp, humorous exploration of contemporary relationships and personal identity.
|
E2068304
|
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: All She Wants | Statement: [Jonathan Harvey, wroteNovel, All She Wants]
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: All She Wants Triple: [Jonathan Harvey, wroteNovel, All She Wants]
Generated description
All She Wants is a novel by British writer Jonathan Harvey, known for its sharp, humorous exploration of contemporary relationships and personal identity.
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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb5571988190bc28f07f2314bb23 |
completed | May 3, 2026, 7:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36657332ec8190acb9b5a0d59448d1 |
completed | June 20, 2026, 10:03 a.m. |
| NEDg | Description generation | batch_6a3666dc6378819091919dd33cc0f7ab |
completed | June 20, 2026, 10:09 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a3667bd9ea48190b373a780b3700891 |
completed | June 20, 2026, 10:13 a.m. |
Created at: May 1, 2026, 1:44 a.m.