Triple
T17688430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadaijin |
E440957
|
entity |
| Predicate | nativeLabel |
P657
|
FINISHED |
| Object | 左大臣 |
—
|
NE NERFINISHED |
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: [Sadaijin, nativeLabel, 左大臣]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 左大臣 Context triple: [Sadaijin, nativeLabel, 左大臣]
-
A.
Sadaijin (Minister of the Left)
chosen
Sadaijin (Minister of the Left) was one of the highest-ranking officials in Japan’s classical imperial government, serving as a chief minister alongside the Udaijin (Minister of the Right) in the ritsuryō administrative system.
-
B.
Udaijin (Minister of the Right)
Udaijin (Minister of the Right) was one of the highest-ranking officials in Japan’s classical imperial government, serving as a chief minister directly under the emperor within the ritsuryō administrative system.
-
C.
内閣府特命担当大臣
内閣府特命担当大臣は、日本の内閣府において特定分野の政策を担当するために任命される国務大臣の役職です。
-
D.
藤原道長
藤原道長は、平安時代中期に摂関政治の最盛期を築き上げた藤原氏の有力貴族であり、娘たちを天皇の后に立てることで絶大な権勢を振るった人物である。
-
E.
逓信大臣
逓信大臣は、日本の旧逓信省を統括し郵便・電信・電話などの通信行政を担当した国務大臣の役職である。
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704944d8819089b153aa14839fc0 |
completed | April 19, 2026, 6:03 a.m. |
Created at: April 10, 2026, 10:03 a.m.