Triple
T34084958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nifty Fifty |
E874153
|
entity |
| Predicate | hasDerivativeInstruments |
P155401
|
FINISHED |
| Object | index futures |
—
|
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: index futures | Statement: [Nifty Fifty, hasDerivativeInstruments, index futures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerivativeInstruments Context triple: [Nifty Fifty, hasDerivativeInstruments, index futures]
-
A.
isUsedForDerivatives
Indicates that something serves as a basis, input, or underlying component for creating or calculating derivatives.
-
B.
hasDerivatives
Indicates that one entity is derived, obtained, or developed from another entity.
-
C.
hasDerivativesListedOn
Indicates that financial derivative instruments based on an underlying asset or entity are listed and traded on a specified exchange or trading venue.
-
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.
hasDerivativesBasedOnIt
chosen
Indicates that one entity serves as the basis or source from which one or more derivative entities are created or derived.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 1, 2026, 1:52 a.m.