Triple
T5002372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 摺鉢山 |
E112402
|
entity |
| Predicate | 軍事的重要性 |
P27512
|
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.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
-
C.
militaryContext
Indicates that the relationship or action occurs within a military setting, framework, or operational environment.
-
D.
hasMilitarySignificance
chosen
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
-
E.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.