Triple
T37112646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ^BSESN |
E919031
|
entity |
| Predicate | underlyingOf |
P16091
|
FINISHED |
| Object | Sensex futures |
—
|
NE NERFINISHED |
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: Sensex futures | Statement: [^BSESN, underlyingOf, Sensex futures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingOf Context triple: [^BSESN, underlyingOf, Sensex futures]
-
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.
underlies
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
D.
underlyingData
Indicates that one entity serves as the foundational or source data upon which another entity is based, derived, or computed.
-
E.
hasUnderlyingAssets
Indicates that one entity is supported, backed, or derived from another entity or set of entities that serve as its foundational assets.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:15 p.m.