Triple
T14411401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gourmet |
E357335
|
entity |
| Predicate | printEditionEndDate |
P102800
|
FINISHED |
| Object | 2009-11 |
—
|
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: 2009-11 | Statement: [Gourmet, printEditionEndDate, 2009-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printEditionEndDate Context triple: [Gourmet, printEditionEndDate, 2009-11]
-
A.
lastEditionDate
chosen
Indicates the date on which the most recent edition or version of an item was created, published, or last updated.
-
B.
lastEdition
Indicates that one entity is the most recent or final edition/version within a series or sequence of editions.
-
C.
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).
-
D.
ceasedDailyPrintEdition
Indicates that an entity has stopped producing its print edition on a daily basis.
-
E.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90c9b3448190aec1608836a5e913 |
completed | April 14, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.