Triple
T10087256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vigil of Christmas |
E215252
|
entity |
| Predicate | dateInGeneralRomanCalendar |
P90410
|
FINISHED |
| Object | 24 December |
—
|
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: 24 December | Statement: [Vigil of Christmas, dateInGeneralRomanCalendar, 24 December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInGeneralRomanCalendar Context triple: [Vigil of Christmas, dateInGeneralRomanCalendar, 24 December]
-
A.
dateInRomanCalendar
chosen
Indicates that a given date is expressed according to the conventions and structure of the ancient Roman calendar system.
-
B.
positionInRomanCalendar
Indicates the ordinal placement or rank that something occupies within the sequence of months or days in the Roman calendar.
-
C.
endTimeInRomanCalendar
Indicates the time at which an event or interval ends, expressed using the Roman calendar system.
-
D.
startTimeInRomanCalendar
Indicates the point in time when an event or interval begins, expressed using the Roman calendar system.
-
E.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04745b48190a77c422eb76b6660 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.