Triple
T34319361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Chuzzlewit |
E880685
|
entity |
| Predicate | completedPublicationDate |
P44445
|
FINISHED |
| Object | 1844 |
—
|
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: 1844 | Statement: [Martin Chuzzlewit, completedPublicationDate, 1844]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedPublicationDate Context triple: [Martin Chuzzlewit, completedPublicationDate, 1844]
-
A.
finalPublicationDate
chosen
Indicates the date on which a work is officially and definitively published in its final form.
-
B.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
C.
publicationCompleted
Indicates that the process of publishing an item (such as a document, work, or release) has been fully finished and made officially available.
-
D.
fullPublicationDate
Indicates the complete calendar date on which something is formally published, including day, month, and year.
-
E.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:57 a.m.