Triple
T662689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Christmas Dinner |
E11790
|
entity |
| Predicate | publicationForm |
P218
|
FINISHED |
| Object | periodical serial |
—
|
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: periodical serial | Statement: [The Christmas Dinner, publicationForm, periodical serial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationForm Context triple: [The Christmas Dinner, publicationForm, periodical serial]
-
A.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
B.
initialPublicationForm
Indicates the original format or medium in which a work was first published.
-
C.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
D.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
E.
publicationStatus
Indicates the current state or phase of a work within its publication lifecycle, such as draft, under review, published, or retired.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd081e8819097f289961f5eff29 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.