Triple
T5534172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | February |
E145118
|
entity |
| Predicate | hasFirstDayNameInLeapYear2020 |
P64778
|
FINISHED |
| Object | Saturday |
—
|
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: Saturday | Statement: [February, hasFirstDayNameInLeapYear2020, Saturday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstDayNameInLeapYear2020 Context triple: [February, hasFirstDayNameInLeapYear2020, Saturday]
-
A.
hasDateInLeapYear
Indicates that the associated date occurs in a leap year.
-
B.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
C.
hasDayCountLeapYear
Indicates that the associated day count value applies specifically to a leap year.
-
D.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
E.
occursAfterLeapMonthInLeapYears
Indicates that the referenced event or time period takes place after the leap month specifically in years that are designated as leap years.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fa0141c81909a216be9f48d64e1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:34 p.m.