Triple
T37707558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecraft Java Edition 1.11 |
E939234
|
entity |
| Predicate | preReleaseDate |
P153675
|
FINISHED |
| Object | 2016-11-08 |
—
|
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: 2016-11-08 | Statement: [Minecraft Java Edition 1.11, preReleaseDate, 2016-11-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preReleaseDate Context triple: [Minecraft Java Edition 1.11, preReleaseDate, 2016-11-08]
-
A.
previewReleaseDate
chosen
Indicates the date on which a preview or pre-release version of something is or was made available.
-
B.
preRelease
Indicates that something occurs, is available, or is done before its official or general release.
-
C.
earlyAccessReleaseDate
Indicates the date on which something is first made available to a limited or pre-release audience before its full public release.
-
D.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
E.
intendedForReleaseIn
Indicates that something is planned or scheduled to be made available or launched within a specified context, such as a time, market, or platform.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.