Triple
T31629830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mäṣḥafä Sa'atat |
E807133
|
entity |
| Predicate | timeOrganization |
P25625
|
FINISHED |
| Object | fixed sequence of hours |
—
|
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: fixed sequence of hours | Statement: [Mäṣḥafä Sa'atat, timeOrganization, fixed sequence of hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOrganization Context triple: [Mäṣḥafä Sa'atat, timeOrganization, fixed sequence of hours]
-
A.
timeTabledBy
Indicates that an event or activity has been scheduled or placed on a timetable by a particular agent or organizing entity.
-
B.
timeStructure
chosen
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
C.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
D.
timeDesignation
Indicates that one entity assigns, specifies, or denotes a particular time or temporal label for another entity or event.
-
E.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 30, 2026, 10:44 p.m.