Triple
T5534171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | February |
E145118
|
entity |
| Predicate | hasFirstDayNameInCommonYear2024 |
P22641
|
FINISHED |
| Object | Thursday |
—
|
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: Thursday | Statement: [February, hasFirstDayNameInCommonYear2024, Thursday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstDayNameInCommonYear2024 Context triple: [February, hasFirstDayNameInCommonYear2024, Thursday]
-
A.
dayName4
Indicates that an entity is associated with the name of the fourth day of the week (e.g., Thursday), expressing a mapping from a day to its conventional name.
-
B.
hasDayNameSystem
Indicates that an entity employs or is associated with a particular system for naming or designating days.
-
C.
nameDayExists
Indicates that there exists a recognized name day associated with a given name (and possibly date or locale).
-
D.
hasNameDay
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
E.
dayName
chosen
Indicates the specific name of the day of the week associated with a given date or time.
- 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_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. |
Created at: March 22, 2026, 3:34 p.m.