Triple
T32924790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baháʼí Era |
E842236
|
entity |
| Predicate | startDateEvent |
P288
|
FINISHED |
| Object | declaration of the Báb |
—
|
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: declaration of the Báb | Statement: [Baháʼí Era, startDateEvent, declaration of the Báb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateEvent Context triple: [Baháʼí Era, startDateEvent, declaration of the Báb]
-
A.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
B.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
-
C.
dateEvent
Indicates that an event takes place or is scheduled on a specific date.
-
D.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
E.
mainEventDate
Indicates the primary or most significant date on which the referenced event occurs or is scheduled to occur.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: May 1, 2026, 1:20 a.m.