Triple
T29575969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Genius in the Family |
E753442
|
entity |
| Predicate | workTitleCharacter |
P86549
|
FINISHED |
| Object | Jacqueline du Pré |
—
|
NE NERFINISHED |
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: Jacqueline du Pré | Statement: [A Genius in the Family, workTitleCharacter, Jacqueline du Pré]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTitleCharacter Context triple: [A Genius in the Family, workTitleCharacter, Jacqueline du Pré]
-
A.
workTitleOfCharacter
Indicates that the specified work (e.g., book, film, game) is the title in which the given character appears.
-
B.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
C.
sourceWorkTitleCharacter
chosen
Indicates that a character appears in, or is associated with, a specific source work identified by its title.
-
D.
titleCharacterString
Indicates that one entity is the textual string representing the title associated with another entity.
-
E.
portrayedTitleCharacter
Indicates that one entity played the main or title role character associated with another entity (such as a work or production).
- F. None of above.
Provenance (3 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:03 p.m.