Triple
T31306929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tavallod-e Baháʼu'lláh |
E798356
|
entity |
| Predicate | isHolyDayFor |
P171557
|
FINISHED |
| Object | followers of Baháʼu'lláh |
—
|
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: followers of Baháʼu'lláh | Statement: [Tavallod-e Baháʼu'lláh, isHolyDayFor, followers of Baháʼu'lláh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHolyDayFor Context triple: [Tavallod-e Baháʼu'lláh, isHolyDayFor, followers of Baháʼu'lláh]
-
A.
hasOfficialHoliday
Indicates that a particular date, event, or period is formally recognized as an official holiday by an authority or governing body.
-
B.
isFederalHoliday
Indicates that a given day is officially recognized as a federal holiday by the national government.
-
C.
mayBeHolyDayOfObligation
Indicates that a given day has the potential status of being a Holy Day of Obligation within a particular religious or canonical context.
-
D.
isHolidayStandard
Indicates that something conforms to or is recognized as a regular, officially established holiday.
-
E.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:14 p.m.