Triple
T37961204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecraft Java Edition Beta 1.3 |
E947011
|
entity |
| Predicate | addedItem |
P189102
|
FINISHED |
| Object | bed item |
—
|
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: bed item | Statement: [Minecraft Java Edition Beta 1.3, addedItem, bed item]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedItem Context triple: [Minecraft Java Edition Beta 1.3, addedItem, bed item]
-
A.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
B.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
C.
addedInUpdate
chosen
Indicates that something was introduced or became available as part of a specific update or version change.
-
D.
associatedItem
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
E.
canBeAddedTo
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.