Triple
T21461832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 陸軍次官 |
E529489
|
entity |
| Predicate | 権限区分 |
P106191
|
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.
authorityRole
chosen
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
B.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
C.
designationGrantsAccessTo
Indicates that holding a particular designation or role grants permission to access a specific resource or capability.
-
D.
authorityInTaxonomy
Indicates that an entity serves as the defining or governing source (authority) for the classification or naming of another entity within a taxonomy.
-
E.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
- 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.