Triple
T36143873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himmel Street bombing |
E1045388
|
entity |
| Predicate | publisherOfFirstEditionContext |
P7323
|
FINISHED |
| Object | Picador |
—
|
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: Picador | Statement: [Himmel Street bombing, publisherOfFirstEditionContext, Picador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfFirstEditionContext Context triple: [Himmel Street bombing, publisherOfFirstEditionContext, Picador]
-
A.
firstPublisher
chosen
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
B.
firstCompleteEditionPublisher
Indicates the publisher responsible for issuing the first complete edition of a work.
-
C.
publisherOfBaseEdition
Indicates the entity that serves as the publisher responsible for the base or original edition of a work.
-
D.
editorOfFirstBookPublication
Indicates that a person or entity served as the editor for the first published edition of a specific book.
-
E.
publisherOfCollectedEdition
Indicates that an entity serves as the publisher responsible for issuing a collected edition of a work or set of works.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:08 p.m.