Triple
T4344602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiroshima Peace Memorial Day |
E97868
|
entity |
| Predicate | languageOfOfficialEvents |
P2769
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Hiroshima Peace Memorial Day, languageOfOfficialEvents, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfOfficialEvents Context triple: [Hiroshima Peace Memorial Day, languageOfOfficialEvents, Japanese]
-
A.
languageOfEvent
Indicates the language in which an event is conducted, presented, or communicated.
-
B.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
C.
languageOfCeremony
chosen
Indicates the language in which a ceremony is conducted or officially performed.
-
D.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
E.
previousOfficialLanguage
Indicates that one language formerly held official status in a country, region, or organization before being replaced or losing that status.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3518aa5cc8190b50f47b1070715fe |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.