Triple
T37961043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecraft Java Edition 1.16 |
E947008
|
entity |
| Predicate | addsToolSet |
P186783
|
FINISHED |
| Object | Netherite tools |
—
|
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 tools | Statement: [Minecraft Java Edition 1.16, addsToolSet, Netherite tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsToolSet Context triple: [Minecraft Java Edition 1.16, addsToolSet, Netherite tools]
-
A.
usesToolFor
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
B.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
C.
addsTechnology
chosen
Indicates that one entity incorporates or introduces a specific technology into another entity, system, or context.
-
D.
regardsAsTool
Indicates that one entity views or treats another entity primarily as an instrument or means to achieve its own goals, rather than as an end in itself.
-
E.
isToolIn
Indicates that a tool is located within or contained inside a specified space, container, or context.
- 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.