Triple
T29975213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | けんこくきねんのひ |
E761423
|
entity |
| Predicate | 祝日名の表記特徴 |
P98437
|
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.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
B.
specialDaysName
Indicates that a special or notable day is identified or labeled with a particular name.
-
C.
traditionalDateInJapan
Indicates that an entity has a specific date expressed in the traditional Japanese calendar system (e.g., era-based or lunisolar date).
-
D.
別表記
chosen
Indicates that one entity is an alternative written form or spelling variant of another entity.
-
E.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
- 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.