Triple
T1975797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SETSqx |
E42907
|
entity |
| Predicate | supportsTradingIn |
P19796
|
FINISHED |
| Object | equities |
—
|
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: equities | Statement: [SETSqx, supportsTradingIn, equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTradingIn Context triple: [SETSqx, supportsTradingIn, equities]
-
A.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
B.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
C.
supportsBuyingChannel
chosen
Indicates that one entity enables, allows, or is compatible with a particular buying or purchasing channel used by another entity.
-
D.
isTradingCenter
Indicates that a place functions as a central hub where goods, services, or financial instruments are actively exchanged or traded.
-
E.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f835108190b0709ccf3a487a96 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.