Triple
T36920529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frazz Davis |
E913183
|
entity |
| Predicate | publicationTypeWorkedFor |
P218
|
FINISHED |
| Object | newspaper |
—
|
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: newspaper | Statement: [Frazz Davis, publicationTypeWorkedFor, newspaper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationTypeWorkedFor Context triple: [Frazz Davis, publicationTypeWorkedFor, newspaper]
-
A.
publicationInWork
Indicates that a specific publication appears within, or is included as part of, a larger work (such as a book, collection, or series).
-
B.
publishedWorksBy
Indicates that one entity has created works that have been made publicly available by another entity (such as an author’s works published by a publisher).
-
C.
publicationOfWork
Indicates that a particular work has been formally made public, typically through printing, distribution, or release by a publisher or similar entity.
-
D.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
E.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: May 3, 2026, 4:13 p.m.