Triple
T1842916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Hazard of New Fortunes |
E41215
|
entity |
| Predicate | publisherWithinStory |
P18285
|
FINISHED |
| Object | Every Other Week |
—
|
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: Every Other Week | Statement: [A Hazard of New Fortunes, publisherWithinStory, Every Other Week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherWithinStory Context triple: [A Hazard of New Fortunes, publisherWithinStory, Every Other Week]
-
A.
publisherInUniverse
chosen
Indicates that a publisher operates, exists, or is recognized within a particular fictional or conceptual universe.
-
B.
publishedAuthor
Indicates that a person is the author of one or more works that have been formally published.
-
C.
publisherRole
Indicates the specific function, capacity, or responsibility an entity has in relation to publishing a work or resource.
-
D.
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).
-
E.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.