Triple
T3063466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Day (Turkey) |
E62048
|
entity |
| Predicate | publicHolidayStatusSince |
P44888
|
FINISHED |
| Object | 1925 |
—
|
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: 1925 | Statement: [Republic Day (Turkey), publicHolidayStatusSince, 1925]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicHolidayStatusSince Context triple: [Republic Day (Turkey), publicHolidayStatusSince, 1925]
-
A.
holidayStatus
Indicates the current holiday-related state or condition associated with an entity, such as whether it is a holiday, non-holiday, or a specific holiday type.
-
B.
publicHolidayScope
Indicates the jurisdictional or contextual scope within which a public holiday is officially recognized or applicable.
-
C.
hasOfficialHoliday
Indicates that a particular date, event, or period is formally recognized as an official holiday by an authority or governing body.
-
D.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
E.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9ea088fc819090b9d5bbcb268671 |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.