Triple
T29120269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QT-1 |
E737159
|
entity |
| Predicate | publicationVenueOfWork |
P309
|
FINISHED |
| Object | Astounding Science Fiction |
—
|
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: Astounding Science Fiction | Statement: [QT-1, publicationVenueOfWork, Astounding Science Fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationVenueOfWork Context triple: [QT-1, publicationVenueOfWork, Astounding Science Fiction]
-
A.
publishingVenue
Indicates the venue (such as a journal, conference, or publisher) where a work is formally published.
-
B.
publisherOfWorkAppearingIn
Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
-
C.
publishedIn
chosen
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
D.
fieldOfPublication
Indicates the academic or topical area in which a work is published.
-
E.
publicationOpus
Indicates that a work or opus has been published, linking the creative work to its publication event or status.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 11:25 a.m.