Triple
T1151524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAC 40 |
E23686
|
entity |
| Predicate | isUsedAsUnderlyingFor |
P16091
|
FINISHED |
| Object | derivatives |
—
|
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: derivatives | Statement: [CAC 40, isUsedAsUnderlyingFor, derivatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedAsUnderlyingFor Context triple: [CAC 40, isUsedAsUnderlyingFor, derivatives]
-
A.
underlyingInstrument
Indicates that one financial instrument serves as the reference or basis for the value, payoff, or structure of another financial instrument.
-
B.
underlyingAsset
chosen
Indicates that one asset serves as the fundamental reference or basis for the value, performance, or contractual terms of another financial instrument or derivative.
-
C.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.