Triple
T23010604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RY |
E572893
|
entity |
| Predicate | isSubjectToMarketRisk |
P150650
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [RY, isSubjectToMarketRisk, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectToMarketRisk Context triple: [RY, isSubjectToMarketRisk, true]
-
A.
hasUnderlyingMarket
Indicates that one entity is based on, derives its value from, or is traded with reference to another entity that serves as its fundamental market.
-
B.
hasInflationRisk
Indicates that something is subject to potential loss of value or purchasing power due to inflation.
-
C.
isSoleSecuritiesMarketOf
Indicates that one securities market is the only market on which a given security or set of securities is traded.
-
D.
hasUnderlyingAssets
Indicates that one entity is supported, backed, or derived from another entity or set of entities that serve as its foundational assets.
-
E.
issuerMarket
Indicates a relationship where a specific market is associated with, or serves as the trading or listing venue for, a given issuer.
- F. None of above. chosen
Provenance (4 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835b0cb881908d3d2dd40cffcbc2 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.