Triple
T31950364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marksville culture |
E815761
|
entity |
| Predicate | tradesFor |
P2914
|
FINISHED |
| Object | Great Lakes copper |
—
|
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: Great Lakes copper | Statement: [Marksville culture, tradesFor, Great Lakes copper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradesFor Context triple: [Marksville culture, tradesFor, Great Lakes copper]
-
A.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
B.
trades
chosen
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
C.
tradedUsing
Indicates that an exchange or trade was conducted by means of a specified instrument, medium, or mechanism.
-
D.
tradedAlong
Indicates that an entity engaged in trade or exchange activities following or using a particular route, path, or corridor.
-
E.
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.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2a905d081909cf5fbedd1181a1a |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.