Triple
T9257669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aramco Trading Company |
E222485
|
entity |
| Predicate | tradingStrategy |
P56458
|
FINISHED |
| Object | Arbitrage trading |
—
|
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: Arbitrage trading | Statement: [Aramco Trading Company, tradingStrategy, Arbitrage trading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingStrategy Context triple: [Aramco Trading Company, tradingStrategy, Arbitrage trading]
-
A.
tradingApproach
chosen
Indicates the method or strategy an entity uses to conduct trading activities or make trade-related decisions.
-
B.
tradingSegment
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
-
C.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
D.
actualTrading
Indicates the occurrence of real, executed trading activity between parties, as opposed to planned, simulated, or potential trades.
-
E.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b660448190b6bc04beff0f5512 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.