Triple
T29975198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | けんこくきねんのひ |
E761423
|
entity |
| Predicate | カレンダー上の位置づけ |
P44231
|
FINISHED |
| Object | 毎年同一日付の祝日 |
—
|
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: 毎年同一日付の祝日 | Statement: [けんこくきねんのひ, カレンダー上の位置づけ, 毎年同一日付の祝日]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: カレンダー上の位置づけ Context triple: [けんこくきねんのひ, カレンダー上の位置づけ, 毎年同一日付の祝日]
-
A.
typicalCalendarPosition
chosen
Indicates the usual or standard placement of something within a calendar sequence, such as its customary date, time, or ordering.
-
B.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
C.
datePlacement
Indicates a temporal relationship specifying when an event or entity is positioned or scheduled in time, such as the assigned or actual date of occurrence.
-
D.
positionInRomanCalendar
Indicates the ordinal placement or rank that something occupies within the sequence of months or days in the Roman calendar.
-
E.
partOfCalendar
Indicates that one temporal element (such as an event, date, or period) belongs to, is contained within, or is scheduled as a component of a particular calendar.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678d44b848190a0c7887baf01b905 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:33 p.m.