Triple
T10605920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nifty IT |
E275874
|
entity |
| Predicate | derivativeInstruments |
P15875
|
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 IT, derivativeInstruments, index futures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivativeInstruments Context triple: [Nifty IT, derivativeInstruments, index futures]
-
A.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
B.
isUsedForDerivatives
Indicates that something serves as a basis, input, or underlying component for creating or calculating derivatives.
-
C.
underlyingInstrument
chosen
Indicates that one financial instrument serves as the reference or basis for the value, payoff, or structure of another financial instrument.
-
D.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
-
E.
derivativesType
Indicates the specific kind or category of derivative relationship that exists between two related 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4a5df88190b993196ca7849a88 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.