Triple
T33210680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rick Dockery |
E850148
|
entity |
| Predicate | authorOfWorkCharacterAppearsIn |
P65216
|
FINISHED |
| Object | John Grisham |
—
|
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: John Grisham | Statement: [Rick Dockery, authorOfWorkCharacterAppearsIn, John Grisham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfWorkCharacterAppearsIn Context triple: [Rick Dockery, authorOfWorkCharacterAppearsIn, John Grisham]
-
A.
publisherOfWorksFeaturingCharacter
Indicates that one entity is the publisher responsible for releasing works in which a given character appears.
-
B.
authorOfWorkHeAppearsIn
chosen
Indicates that a person is the author of a work in which he himself appears as a character or subject.
-
C.
characterAppearsIn
Indicates that a specific character is present or featured within a particular work, such as a book, movie, or episode.
-
D.
appearsInWrittenBy
Indicates that an entity (such as a character, concept, or element) appears in a written work that is authored by a specified creator.
-
E.
characterInBookBy
Indicates that a character appears in a book that was written by a specified author.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:30 a.m.