Triple
T25656708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangladesh Independence Day |
E643255
|
entity |
| Predicate | observedOnDay |
P1160
|
FINISHED |
| Object | 26 |
—
|
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: 26 | Statement: [Bangladesh Independence Day, observedOnDay, 26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedOnDay Context triple: [Bangladesh Independence Day, observedOnDay, 26]
-
A.
observesDay
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
-
B.
dateObserved
chosen
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
-
D.
observedWhen
Indicates that one entity is observed or recorded at a specific time or under particular temporal conditions.
-
E.
alsoObservedOn
Indicates that the same entity, event, or phenomenon was additionally observed on another occasion, date, or context beyond the primary one referenced.
- 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.