Triple
T28650402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonweal |
E725175
|
entity |
| Predicate | hasNotableSerializedWork |
P118326
|
FINISHED |
| Object | News from Nowhere |
—
|
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: News from Nowhere | Statement: [Commonweal, hasNotableSerializedWork, News from Nowhere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSerializedWork Context triple: [Commonweal, hasNotableSerializedWork, News from Nowhere]
-
A.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
B.
notableWorkPublishedIn
chosen
Indicates that a notable work associated with an entity was published in a particular venue, medium, or publication.
-
C.
notableWorkWrittenThere
Indicates that a notable work was written at or in the specified place.
-
D.
hasCatalogedWorkOn
Indicates that an entity has formally recorded, listed, or documented another entity as a work within a catalog or collection.
-
E.
notableWorkContained
Indicates that a notable work is included within or is part of another entity, such as a collection, publication, or compilation.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: April 28, 2026, 4:51 a.m.