Triple
T19884429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Tuesday |
E477859
|
entity |
| Predicate | isDayNumberInEastertide |
P135435
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Easter Tuesday, isDayNumberInEastertide, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDayNumberInEastertide Context triple: [Easter Tuesday, isDayNumberInEastertide, 3]
-
A.
dayRelativeToEaster
Indicates the temporal offset of a given day relative to the date of Easter in a specific year (e.g., days before or after Easter Sunday).
-
B.
isOnEveOf
Indicates that one event, state, or time point occurs immediately before another, typically just prior to its start.
-
C.
isOrdinalDay
chosen
Indicates that a given day is being specified or classified by its ordinal position within a sequence of days (e.g., 1st, 2nd, 3rd day).
-
D.
liturgicalDayPosition
Indicates the specific placement or order of a liturgical day within a liturgical calendar, season, or sequence of observances.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590870908190a18b545f0ff0ccd6 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.