Triple
T21748036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 関東軍司令官 |
E536836
|
entity |
| Predicate | 軍事的地位 |
P65928
|
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.
militaryImportance
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
-
B.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
-
C.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
E.
rankComparedToMilitary
chosen
Indicates a comparison between an entity’s status or position and a specified level or type of military rank.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a77e19c81909bf26f96aa41a7ce |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.