Triple
T37662652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Healing |
E937749
|
entity |
| Predicate | bedrockEditionId |
P188608
|
FINISHED |
| Object | potion 36 (healing) / 38 (healing II) with data values |
—
|
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: potion 36 (healing) / 38 (healing II) with data values | Statement: [Potion of Healing, bedrockEditionId, potion 36 (healing) / 38 (healing II) with data values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bedrockEditionId Context triple: [Potion of Healing, bedrockEditionId, potion 36 (healing) / 38 (healing II) with data values]
-
A.
bedrockEditionID
chosen
Indicates the identifier that links something specifically to its Bedrock Edition version or instance.
-
B.
bedrockEditionAvailability
Indicates whether something is available or supported in the Bedrock Edition of a product or system.
-
C.
javaEditionID
Indicates that one entity is identified as the specific Java edition identifier associated with another entity.
-
D.
serverEdition
Indicates the specific edition or variant of a server within a broader server product or family.
-
E.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
- 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_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.