Triple
T34084999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSE: BANKNIFTY |
E874154
|
entity |
| Predicate | derivativesVenue |
P172854
|
FINISHED |
| Object | NSE F&O segment |
—
|
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: NSE F&O segment | Statement: [NSE: BANKNIFTY, derivativesVenue, NSE F&O segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivativesVenue Context triple: [NSE: BANKNIFTY, derivativesVenue, NSE F&O segment]
-
A.
isCentralVenueOf
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
B.
isTradingVenueFor
chosen
Indicates that one entity functions as a marketplace or platform where another entity’s financial instruments or assets are bought and sold.
-
C.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
D.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
E.
usesTradingVenues
Indicates that one entity conducts trading activities through, or executes trades on, specific trading venues associated with another entity.
- 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_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:52 a.m.