Triple
T17768710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1Q84 |
E443575
|
entity |
| Predicate | publicationDetail |
P128857
|
FINISHED |
| Object | Book 1 first published in 2009 |
—
|
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: Book 1 first published in 2009 | Statement: [1Q84, publicationDetail, Book 1 first published in 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationDetail Context triple: [1Q84, publicationDetail, Book 1 first published in 2009]
-
A.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
-
B.
publicationBody
Indicates the organization or entity that serves as the publishing body responsible for issuing the referenced work.
-
C.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
D.
publicationTitle
Indicates the name or title under which a work (such as an article, book, or paper) is formally published.
-
E.
publicationCollection
Indicates that one entity is a collection or grouping that contains or organizes multiple publication entities.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fd8aa081909c8ee9264af15c69 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:11 a.m.