Triple
T21461837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 陸軍次官 |
E529489
|
entity |
| Predicate | 継承・類似役職 |
P36906
|
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.
successorRole
chosen
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
B.
successionRole
Indicates a role or position that one entity assumes as the successor to another in a sequence of holders or office-bearers.
-
C.
roleSimilarTo
Indicates that two entities have roles or functions that are alike or closely comparable in nature or responsibility.
-
D.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
-
E.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ef0c0881908554977df00604a6 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.