Triple
T13654067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avery |
E326811
|
entity |
| Predicate | publishesBooksOn |
P110995
|
FINISHED |
| Object | health |
—
|
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: health | Statement: [Avery, publishesBooksOn, health]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesBooksOn Context triple: [Avery, publishesBooksOn, health]
-
A.
publishesAuthor
Indicates that a publisher or publishing entity issues, releases, or makes publicly available works created by a specific author.
-
B.
workPublishedAuthor
Indicates that a particular work was created and published by a specific author.
-
C.
workPublishedBy
Indicates that a work (such as a book, article, or other creation) has been issued or made publicly available by a particular publisher or publishing entity.
-
D.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
E.
publishingPlatform
Indicates that one entity serves as the medium or service through which another entity is published or made publicly available.
- F. None of above. chosen
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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60ace048190a4b92310ba272bd1 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:52 p.m.