Triple
T9517977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nayrouz |
E229572
|
entity |
| Predicate | timeInCopticCalendar |
P88503
|
FINISHED |
| Object | 1 Thout |
—
|
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: 1 Thout | Statement: [Nayrouz, timeInCopticCalendar, 1 Thout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInCopticCalendar Context triple: [Nayrouz, timeInCopticCalendar, 1 Thout]
-
A.
timeInSolarCalendar
Indicates that a specified time or date is expressed according to a solar-based calendar system rather than another type of calendar.
-
B.
CopticChristmasCorrespondsTo
Indicates that a given date or event corresponds to, or falls on, the day of Coptic Christmas in the Coptic liturgical calendar.
-
C.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
timeRelativeToFeast
Indicates the temporal relationship of an event or state with respect to a specific feast, such as occurring before, during, or after that feast.
-
E.
dateInEasternOrthodoxChurches
Indicates that the specified date is observed or used according to the liturgical calendar of Eastern Orthodox churches.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9880417c819097dde277988df36d |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:59 p.m.