Triple
T19943251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National POW MIA Recognition Day |
E479358
|
entity |
| Predicate | typicalDayOfWeekOfObservation |
P34404
|
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: [National POW MIA Recognition Day, typicalDayOfWeekOfObservation, Friday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDayOfWeekOfObservation Context triple: [National POW MIA Recognition Day, typicalDayOfWeekOfObservation, Friday]
-
A.
observesDay
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
-
B.
dayType
Indicates the classification or category of a given day based on its characteristics or role (e.g., weekday, weekend, holiday).
-
C.
typicalEventDay
chosen
Indicates the day on which an event is normally or most commonly held or occurs.
-
D.
mentionsDayOfWeek
Indicates that something explicitly refers to or names a specific day of the week.
-
E.
typicalFrequencyWeekdayDaytime
Indicates the usual or most common frequency with which something occurs during daytime hours on weekdays.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a63f2e48190ba1cb7a4f415e7f6 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.