Triple
T30397068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musket Wars |
E773246
|
entity |
| Predicate | tradedUsing |
P169159
|
FINISHED |
| Object | flax |
—
|
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: flax | Statement: [Musket Wars, tradedUsing, flax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradedUsing Context triple: [Musket Wars, tradedUsing, flax]
-
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.
tradedAlong
Indicates that an entity engaged in trade or exchange activities following or using a particular route, path, or corridor.
-
C.
isTradedBy
Indicates that an item, asset, or resource is exchanged or dealt with by a particular agent, party, or trading entity.
-
D.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
E.
isTradedLike
Indicates that one entity is exchanged, valued, or handled in markets in a manner similar to another entity.
- F. None of above. chosen
Provenance (4 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685aef340819081190a2397b94251 |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:02 p.m.