Triple
T37664953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crying Obsidian |
E937799
|
entity |
| Predicate | barterItem |
P178182
|
FINISHED |
| Object | gold ingot |
—
|
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: gold ingot | Statement: [Crying Obsidian, barterItem, gold ingot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barterItem Context triple: [Crying Obsidian, barterItem, gold ingot]
-
A.
tradeInvolves
chosen
Indicates that a trade or exchange relationship exists between the referenced entities, where goods, services, or value are transferred among them.
-
B.
usedItem
Indicates that an entity has utilized or employed a particular item for some purpose.
-
C.
isTradeable
Indicates that an entity can be bought, sold, or exchanged within a market or trading system.
-
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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e001c88190912781fa9a84f246 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.