Triple
T9194502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony Buddenbrook |
E220668
|
entity |
| Predicate | publicationContextWorkFirstPublished |
P47750
|
FINISHED |
| Object | 1901 |
—
|
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: 1901 | Statement: [Tony Buddenbrook, publicationContextWorkFirstPublished, 1901]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationContextWorkFirstPublished Context triple: [Tony Buddenbrook, publicationContextWorkFirstPublished, 1901]
-
A.
firstPublicationContext
Indicates the original context or setting (such as venue, medium, or circumstance) in which something was first published.
-
B.
placeOfFirstPublication
Indicates the location where a work was first published or made publicly available.
-
C.
firstPublicationIn
chosen
Indicates the initial venue, medium, or context in which a work was first published.
-
D.
firstPublishedWith
Indicates that an entity was initially published together with another specified entity, sharing the same first publication event.
-
E.
originalPublicationOfWholeWork
Indicates that one entity is the original publication in which an entire work was first made publicly available.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5c3614c81909e26417e00fdfa11 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.