Triple
T37665284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End stone bricks |
E937806
|
entity |
| Predicate | gameVersionIntroduced |
P181744
|
FINISHED |
| Object | Minecraft Java Edition 1.9 |
—
|
NE NERFINISHED |
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 Java Edition 1.9 | Statement: [End stone bricks, gameVersionIntroduced, Minecraft Java Edition 1.9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameVersionIntroduced Context triple: [End stone bricks, gameVersionIntroduced, Minecraft Java Edition 1.9]
-
A.
introducedVersionOf
chosen
Indicates that one entity is the version in which another entity was first introduced or made available.
-
B.
introducedInGameAs
Indicates that an entity first appeared or was made available within a specific game title.
-
C.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
D.
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.
-
E.
introducedInPatch
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.