Triple
T3632535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjy Compson |
E76989
|
entity |
| Predicate | renamedReason |
P2136
|
FINISHED |
| Object | family embarrassment over Uncle Maury |
—
|
LITERAL 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: family embarrassment over Uncle Maury | Statement: [Benjy Compson, renamedReason, family embarrassment over Uncle Maury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedReason Context triple: [Benjy Compson, renamedReason, family embarrassment over Uncle Maury]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
C.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
D.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
E.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30251d881908284edeb7fe69ad8 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.