Triple
T15096244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BATRA |
E360544
|
entity |
| Predicate | subjectToMarketRisk |
P107958
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [BATRA, subjectToMarketRisk, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToMarketRisk Context triple: [BATRA, subjectToMarketRisk, yes]
-
A.
currencyRisk
Indicates the exposure an entity has to potential financial loss or gain due to fluctuations in foreign exchange rates between currencies.
-
B.
hasUnderlyingMarket
chosen
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.
-
C.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
D.
hasInflationRisk
Indicates that something is subject to potential loss of value or purchasing power due to inflation.
-
E.
riskRequirement
Indicates that one entity specifies or imposes a required level or type of risk consideration that another entity must meet or address.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005466e9c8190a68e1fbeb8922b1a |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.