Triple
T5680661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq-100 futures |
E125189
|
entity |
| Predicate | marginingSystem |
P15884
|
FINISHED |
| Object | daily mark-to-market |
—
|
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: daily mark-to-market | Statement: [Nasdaq-100 futures, marginingSystem, daily mark-to-market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marginingSystem Context triple: [Nasdaq-100 futures, marginingSystem, daily mark-to-market]
-
A.
marginSystem
Indicates a financial arrangement where securities are bought or held using borrowed funds, with the securities themselves serving as collateral under a defined margin framework.
-
B.
margining
chosen
Indicates the process of posting, adjusting, or settling collateral (margin) between parties to secure obligations in a financial transaction or trading relationship.
-
C.
marginStyle
Indicates how the margins around an element are styled or configured in relation to surrounding content.
-
D.
leafMargin
Indicates the type or pattern of the edge or border of a leaf (e.g., smooth, serrated, lobed).
-
E.
marginType
Indicates the type or category of margin applied in a given context, such as financial, layout, or safety margin.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.