Triple
T27030206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Thursday |
E680896
|
entity |
| Predicate | affectedAssetClass |
P167292
|
FINISHED |
| Object | precious metals |
—
|
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: precious metals | Statement: [Silver Thursday, affectedAssetClass, precious metals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedAssetClass Context triple: [Silver Thursday, affectedAssetClass, precious metals]
-
A.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
-
B.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
C.
affectedClass
chosen
Indicates that one entity (typically a change, event, or issue) has an impact on or is relevant to a particular class or category of items.
-
D.
assetClassLabel
Indicates the classification category or type assigned to an asset within a broader asset taxonomy.
-
E.
assetClassesTraded
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 7:13 a.m.