Triple
T30282520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The World of Null-A |
E770139
|
entity |
| Predicate | publisherBookEdition |
P132193
|
FINISHED |
| Object | Simon & Schuster |
—
|
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: Simon & Schuster | Statement: [The World of Null-A, publisherBookEdition, Simon & Schuster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherBookEdition Context triple: [The World of Null-A, publisherBookEdition, Simon & Schuster]
-
A.
publishedEdition
Indicates that one entity is a specific edition or version that has been formally published of another work or resource.
-
B.
laterEditionPublisherOfWork
chosen
Indicates that a publisher is responsible for issuing a later edition of a previously existing work.
-
C.
authoritativeEditionPublisher
Indicates that an entity is the publisher responsible for issuing the authoritative or officially recognized edition of a work.
-
D.
editionPublicationYear
Indicates the calendar year in which a particular edition of a work was published.
-
E.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 29, 2026, 7:45 p.m.