Triple
T33053962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Strike |
E845800
|
entity |
| Predicate | inUniverseHolidayDate |
P182278
|
FINISHED |
| Object | December 23 |
—
|
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: December 23 | Statement: [The Strike, inUniverseHolidayDate, December 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseHolidayDate Context triple: [The Strike, inUniverseHolidayDate, December 23]
-
A.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
B.
isHolyDayFor
Indicates that a particular day is recognized or observed as a religiously significant or sacred day for a given entity or group.
-
C.
hasHolidayCountry
Indicates that a specific holiday is officially observed or associated with a particular country.
-
D.
containsHolidayInUnitedStates
Indicates that the referenced time period or schedule includes at least one officially recognized holiday in the United States.
-
E.
isHolidayStandard
Indicates that something conforms to or is recognized as a regular, officially established holiday.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:24 a.m.