Triple
T37961044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecraft Java Edition 1.16 |
E947008
|
entity |
| Predicate | addsArmorSet |
P116169
|
FINISHED |
| Object | Netherite armor |
—
|
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: Netherite armor | Statement: [Minecraft Java Edition 1.16, addsArmorSet, Netherite armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsArmorSet Context triple: [Minecraft Java Edition 1.16, addsArmorSet, Netherite armor]
-
A.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
B.
armorGeneration
chosen
Indicates the creation or provision of protective armor for an entity, often as a result of some action, ability, or process.
-
C.
armorVariant
Indicates that one armor is a specific version, type, or modification derived from another armor.
-
D.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
-
E.
wearsArmorOf
Indicates that one entity is equipped with or dressed in the specific armor that belongs to or is associated with another entity.
- 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_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.