Triple
T10113532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration of the Báb |
E218298
|
entity |
| Predicate | timeOfDayOfEvent |
P6019
|
FINISHED |
| Object | evening |
—
|
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: evening | Statement: [Declaration of the Báb, timeOfDayOfEvent, evening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDayOfEvent Context triple: [Declaration of the Báb, timeOfDayOfEvent, evening]
-
A.
approximateTimeOfDayOfEventCommemorated
Indicates the general time of day during which the commemorated event is understood to have occurred.
-
B.
timeOfCelebration
Indicates the specific time or period during which a celebration takes place.
-
C.
hasTimeOfDay
chosen
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
-
D.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
E.
timeCharacteristic
Indicates a relationship where one entity specifies a temporal property, feature, or constraint that characterizes another entity or event.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ed28081909a812e0634799ef8 |
completed | April 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.