Triple
T31379303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannes Graff |
E800401
|
entity |
| Predicate | associatedWithAuthorDebut |
P176656
|
FINISHED |
| Object | John Irving |
E44109
|
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: John Irving | Statement: [Hannes Graff, associatedWithAuthorDebut, John Irving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAuthorDebut Context triple: [Hannes Graff, associatedWithAuthorDebut, John Irving]
-
A.
literarySeriesDebut
Indicates the work in which a literary series first appeared or was initially introduced.
-
B.
writerOfDebut
chosen
Indicates that one entity is the author who wrote the other entity as their first published work or debut piece.
-
C.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
D.
hasDebutStatusForAuthor
Indicates that an author’s work or appearance is identified as their first (debut) instance in a given context.
-
E.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
- F. None of above.
Provenance (4 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b1442e09c81909528414af4c5ac1b |
completed | June 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:18 p.m.