Triple
T29975214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | けんこくきねんのひ |
E761423
|
entity |
| Predicate | 祝日名の表記理由 |
P168723
|
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.
officialNameInRomaji
Indicates that an entity’s official name is written using the Roman alphabet (romaji) representation.
-
B.
traditionalDateInJapan
Indicates that an entity has a specific date expressed in the traditional Japanese calendar system (e.g., era-based or lunisolar date).
-
C.
hasNameDayOrReligiousUsage
Indicates that an entity has an associated name day celebration or is used in a religious or liturgical context.
-
D.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
E.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
- 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_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_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 6:33 p.m.