Triple
T12474183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Futures Exchange |
E298133
|
entity |
| Predicate | tradedAssetClass |
P67186
|
FINISHED |
| Object | interest rates |
—
|
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: interest rates | Statement: [Sydney Futures Exchange, tradedAssetClass, interest rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradedAssetClass Context triple: [Sydney Futures Exchange, tradedAssetClass, interest rates]
-
A.
assetClassesTraded
chosen
Indicates that an entity trades, deals in, or is involved with specific categories or classes of financial assets.
-
B.
tradedAsset
Indicates that an entity is the asset or instrument being exchanged in a trade transaction between parties.
-
C.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
-
D.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
E.
instrumentClassification
Indicates that one entity is classified as a particular type or category of instrument in relation to 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.