Triple
T34085002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSE: BANKNIFTY |
E874154
|
entity |
| Predicate | includesSecuritiesType |
P40808
|
FINISHED |
| Object | bank stocks |
—
|
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: bank stocks | Statement: [NSE: BANKNIFTY, includesSecuritiesType, bank stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSecuritiesType Context triple: [NSE: BANKNIFTY, includesSecuritiesType, bank stocks]
-
A.
includesSecurities
Indicates that one entity contains or comprises one or more securities as part of its composition or holdings.
-
B.
allowsEquitySecurities
Indicates that one party grants permission for the issuance, holding, trading, or other use of equity securities by or for another party.
-
C.
typeOfSecurityTraded
chosen
Indicates the specific kind or category of security that is being traded in a financial transaction.
-
D.
includesFundType
Indicates that one entity contains or encompasses a particular type or category of fund within its scope or structure.
-
E.
hasFinancialInstrumentType
Indicates that an entity is associated with, or classified by, a specific type or category of financial instrument.
- 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.