Triple
T25656785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangabda |
E643256
|
entity |
| Predicate | newYearObservedOn |
P51416
|
FINISHED |
| Object | mid-April (Gregorian calendar) |
—
|
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: mid-April (Gregorian calendar) | Statement: [Bangabda, newYearObservedOn, mid-April (Gregorian calendar)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newYearObservedOn Context triple: [Bangabda, newYearObservedOn, mid-April (Gregorian calendar)]
-
A.
newYearObservedIn
Indicates that a particular New Year celebration or observance takes place in or is recognized within a specified location or region.
-
B.
newYearOccursIn
chosen
Indicates that the celebration or observance of New Year takes place within a specified temporal or calendrical context (such as a particular month, season, or year).
-
C.
newYearDateGregorian
Indicates the specific calendar date on which New Year’s Day occurs according to the Gregorian calendar.
-
D.
newYearCoincidesWith
Indicates that the occurrence of a new year happens at the same time as another specified event or time period.
-
E.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faebdbf08190ab8856d10be8abd1 |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 6:34 p.m.