Triple
T17517674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLEX |
E426606
|
entity |
| Predicate | canBeTradedFor |
P9052
|
FINISHED |
| Object | in-game ISK |
—
|
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: in-game ISK | Statement: [PLEX, canBeTradedFor, in-game ISK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTradedFor Context triple: [PLEX, canBeTradedFor, in-game ISK]
-
A.
tradableFrom
Indicates that something can be traded or exchanged starting from a specified source or origin.
-
B.
isTradedLike
Indicates that one entity is exchanged, valued, or handled in markets in a manner similar to another entity.
-
C.
sharesTradedFor
Indicates that shares of one entity are exchanged or traded in return for another asset, security, or form of consideration.
-
D.
usedForTradeBetween
Indicates that something serves as a medium, instrument, or basis for trade or exchange between two or more parties.
-
E.
canBePurchasedWith
chosen
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.