Triple
T5892274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 栗林忠道 |
E131017
|
entity |
| Predicate | 戦術的特徴 |
P50132
|
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.
tacticalStyle
chosen
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
B.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
militaryCharacteristic
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
D.
hasTacticalMobility
Indicates the capability of an entity to move or be repositioned quickly and effectively within a tactical or operational context.
-
E.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.