Triple
T31529537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of the Coptic New Year |
E804438
|
entity |
| Predicate | calendarEraStart |
P16736
|
FINISHED |
| Object | AD 284 |
—
|
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: AD 284 | Statement: [Feast of the Coptic New Year, calendarEraStart, AD 284]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarEraStart Context triple: [Feast of the Coptic New Year, calendarEraStart, AD 284]
-
A.
calendarEpoch
chosen
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
B.
calendarEraAlignment
Indicates that two calendar eras are related by a defined temporal correspondence or offset, aligning their dates or time scales to each other.
-
C.
endDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which the first use of something ended or ceased.
-
D.
startEraInJapaneseCalendar
Indicates the point in time when a specific era begins within the Japanese calendar system.
-
E.
startDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which something was first put into use or began to be used.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10 p.m.