Triple
T37665068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The End |
E937801
|
entity |
| Predicate | fullyReleasedInVersion |
P181744
|
FINISHED |
| Object | Minecraft 1.0.0 |
—
|
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: Minecraft 1.0.0 | Statement: [The End, fullyReleasedInVersion, Minecraft 1.0.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyReleasedInVersion Context triple: [The End, fullyReleasedInVersion, Minecraft 1.0.0]
-
A.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
-
B.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
C.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
-
D.
introducedVersionOf
chosen
Indicates that one entity is the version in which another entity was first introduced or made available.
-
E.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e001c88190912781fa9a84f246 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.