Triple
T33343788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendl’s pastries |
E853741
|
entity |
| Predicate | releaseContextYear |
P188910
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Mendl’s pastries, releaseContextYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseContextYear Context triple: [Mendl’s pastries, releaseContextYear, 2014]
-
A.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
釈放年
Indicates the year in which an entity is released or set free.
-
C.
fullReleaseYear
Indicates the calendar year in which something is fully released or made publicly available in its complete form.
-
D.
finalReleaseYear
Indicates the calendar year in which something (such as a product, work, or version) is officially released for the last time.
-
E.
eligibleReleaseYear
Indicates the year in which something qualifies or is permitted to be released according to specified criteria or rules.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 1, 2026, 1:34 a.m.