Triple
T16141738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plains (later period) |
E391672
|
entity |
| Predicate | tradeFeature |
P92951
|
FINISHED |
| Object | horse trade among tribes |
—
|
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: horse trade among tribes | Statement: [Plains (later period), tradeFeature, horse trade among tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeFeature Context triple: [Plains (later period), tradeFeature, horse trade among tribes]
-
A.
tradeMechanism
Indicates the method or system through which a trade or exchange between parties is conducted.
-
B.
tradeAspect
Indicates a relationship where one entity is associated with a specific aspect, feature, or dimension of a trade or commercial transaction.
-
C.
hasTradeCharacteristic
chosen
Indicates that an entity possesses a specific trade-related attribute, quality, or feature.
-
D.
tradeSystem
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
-
E.
tradeHubWith
Indicates that one entity functions as a central location or node for trading activities in connection with another entity.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a087c848190aba9ed2ccb422427 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.