Triple
T1450461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mixtec civilization |
E31277
|
entity |
| Predicate | traded |
P2914
|
FINISHED |
| Object | precious metals |
—
|
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: precious metals | Statement: [Mixtec civilization, traded, precious metals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traded Context triple: [Mixtec civilization, traded, precious metals]
-
A.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
-
B.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
C.
trades
chosen
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
D.
tradedSince
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
E.
sharesTradedFor
Indicates that shares of one entity are exchanged or traded in return for another asset, security, or form of consideration.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55d923c8190957756f834f94462 |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.