Triple
T9418733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Báb |
E227093
|
entity |
| Predicate | declaredMissionDate |
P88751
|
FINISHED |
| Object | 1844-05-23 |
—
|
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: 1844-05-23 | Statement: [the Báb, declaredMissionDate, 1844-05-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredMissionDate Context triple: [the Báb, declaredMissionDate, 1844-05-23]
-
A.
mandateConfirmedDate
Indicates the date on which a mandate (such as an authorization or directive) was formally confirmed or validated.
-
B.
datePlanned
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
C.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
D.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
-
E.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68cd1e3481909abcb715e2398120 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:48 p.m.