Triple
T6337599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 重光 葵 |
E142529
|
entity |
| Predicate | 最もよく知られている事績 |
P25528
|
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.
notableDeed
Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
-
B.
mostFamouslyRecordedBy
Indicates that an item (such as a work, song, or performance) is best known or most widely associated with having been recorded by a particular entity.
-
C.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
D.
famousForEvent
chosen
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
E.
traditionallyKnownFor
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654e11988190b708426d3003716a |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.