Triple
T30725785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hob.I:45 |
E782275
|
entity |
| Predicate | hasNicknameOfWork |
P101523
|
FINISHED |
| Object | Farewell |
—
|
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: Farewell | Statement: [Hob.I:45, hasNicknameOfWork, Farewell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNicknameOfWork Context triple: [Hob.I:45, hasNicknameOfWork, Farewell]
-
A.
associatedNicknameOfWork
chosen
Indicates that a given nickname or informal title is commonly used to refer to a particular work.
-
B.
nameSharesWithWork
Indicates that an entity shares the same name as a specified work (such as a book, film, or other creative piece).
-
C.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
D.
hasFullNameInWork
Indicates that an entity is referred to by a specific full name within a particular work or publication.
-
E.
hasGivenNameInWork
Indicates that a work specifies or uses a particular given (first) name for an entity or character.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:36 p.m.