Triple
T38252167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Therese Belivet |
E1014078
|
entity |
| Predicate | aliasOfWork |
P101523
|
FINISHED |
| Object | The Price of Salt (also published as Carol) |
—
|
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: The Price of Salt (also published as Carol) | Statement: [Therese Belivet, aliasOfWork, The Price of Salt (also published as Carol)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aliasOfWork Context triple: [Therese Belivet, aliasOfWork, The Price of Salt (also published as Carol)]
-
A.
aliasOfOccupation
Indicates that one occupation term is an alternative name or alias for another occupation.
-
B.
associatedNicknameOfWork
chosen
Indicates that a given nickname or informal title is commonly used to refer to a particular work.
-
C.
aliasRole
Indicates that one role serves as an alternative or equivalent designation for another role.
-
D.
subjectAlias
Indicates that one entity is an alternative name, label, or alias referring to the same subject as another entity.
-
E.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.