Triple
T33231988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Logic Named Joe |
E850718
|
entity |
| Predicate | hasBeenReprintedIn |
P184029
|
FINISHED |
| Object | various science fiction anthologies |
—
|
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: various science fiction anthologies | Statement: [A Logic Named Joe, hasBeenReprintedIn, various science fiction anthologies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenReprintedIn Context triple: [A Logic Named Joe, hasBeenReprintedIn, various science fiction anthologies]
-
A.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related entity.
-
B.
typeOfWorkReprinted
Indicates that one work is a reprint or reissued version of another original work.
-
C.
reprintPublisher
Indicates that an entity serves as the publisher responsible for issuing a reprinted edition of a work.
-
D.
printedInSeries
Indicates that a work was published as part of a particular series or serial publication.
-
E.
laterEditions
Indicates that one entity is a subsequent or more recent edition of another entity.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 1, 2026, 1:30 a.m.