Triple
T2420000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishiwara Kanji |
E53395
|
entity |
| Predicate | typeOfMilitaryPerson |
P9463
|
FINISHED |
| Object | staff officer |
—
|
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: staff officer | Statement: [Ishiwara Kanji, typeOfMilitaryPerson, staff officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMilitaryPerson Context triple: [Ishiwara Kanji, typeOfMilitaryPerson, staff officer]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
C.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
D.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
E.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.