Triple
T34085010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSE: BANKNIFTY |
E874154
|
entity |
| Predicate | hasEndOfDayData |
P192937
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NSE: BANKNIFTY, hasEndOfDayData, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndOfDayData Context triple: [NSE: BANKNIFTY, hasEndOfDayData, true]
-
A.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
B.
isFinalHourOf
Indicates that one time period represents the last hour within the duration or schedule of another time-related entity.
-
C.
hasDailyMarket
Indicates that an entity regularly hosts or participates in a market that operates on a daily basis.
-
D.
hasEndOfEarningsRange
Indicates that an entity’s earnings are bounded above by a specified maximum value in a defined range.
-
E.
hasTradingDays
Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
- F. None of above. chosen
Provenance (4 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_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 1, 2026, 1:52 a.m.