Triple
T21461807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 陸軍次官 |
E529489
|
entity |
| Predicate | 権限分野 |
P49097
|
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.
areaOfAuthority
chosen
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
-
B.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
C.
hasLimitedAuthorityOver
Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
-
D.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
E.
authorityConsolidation
Indicates the process by which decision-making power and control become increasingly concentrated in a single actor, group, or institution, reducing the influence of others.
- 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.