Triple
T29320072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velli |
E743491
|
entity |
| Predicate | ISOWeekdayEquivalent |
P22641
|
FINISHED |
| Object | Friday |
—
|
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: Friday | Statement: [Velli, ISOWeekdayEquivalent, Friday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISOWeekdayEquivalent Context triple: [Velli, ISOWeekdayEquivalent, Friday]
-
A.
hasISOWeekdayNumber
Indicates the association between a day and its corresponding ISO-standard weekday number (1 for Monday through 7 for Sunday).
-
B.
dayName
chosen
Indicates the specific name of the day of the week associated with a given date or time.
-
C.
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).
-
D.
startDayOfWeek
Indicates the specific day of the week on which a given period, schedule, or recurring event begins.
-
E.
isOrdinalDay
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).
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665ef0d388190a0d3a2169e6254f2 |
completed | May 2, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:22 p.m.