Triple
T6398989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deposition of the Robe of the Mother of God |
E144011
|
entity |
| Predicate | hasDateInJulianCalendar |
P70407
|
FINISHED |
| Object | July 2 |
—
|
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: July 2 | Statement: [Deposition of the Robe of the Mother of God, hasDateInJulianCalendar, July 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDateInJulianCalendar Context triple: [Deposition of the Robe of the Mother of God, hasDateInJulianCalendar, July 2]
-
A.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
B.
hasDateInLeapYear
Indicates that the associated date occurs in a leap year.
-
C.
accuracyComparedToJulian
Indicates how the accuracy of something compares to that of the Julian calendar as a reference standard.
-
D.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
E.
hasLeapMonth
Indicates that a given calendar year includes an extra (intercalary) month beyond the standard set of months.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06897ebc48190842d48cce469eba5 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:35 p.m.