Triple
T11794524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piglin |
E280470
|
entity |
| Predicate | tradesPossibleItems |
P26480
|
FINISHED |
| Object | obsidian |
—
|
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: obsidian | Statement: [Piglin, tradesPossibleItems, obsidian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradesPossibleItems Context triple: [Piglin, tradesPossibleItems, obsidian]
-
A.
tradableFrom
Indicates that something can be traded or exchanged starting from a specified source or origin.
-
B.
productsTraded
chosen
Indicates that one entity exchanges or deals specific goods or commodities with another entity.
-
C.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
D.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
-
E.
tradeMechanism
Indicates the method or system through which a trade or exchange between parties is conducted.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a082d08190a42541396a06ed98 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.