Triple
T21748016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 関東軍司令官 |
E536836
|
entity |
| Predicate | 主な任務 |
P68
|
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.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
B.
laterPrimaryMission
Indicates that one mission occurs after another mission in the sequence of primary missions.
-
C.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
D.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
-
E.
mission
chosen
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
- 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.