Triple
T35351450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mineichi Koga |
E1020890
|
entity |
| Predicate | militaryRankAtPromotion |
P192176
|
FINISHED |
| Object | full admiral |
—
|
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: full admiral | Statement: [Mineichi Koga, militaryRankAtPromotion, full admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRankAtPromotion Context triple: [Mineichi Koga, militaryRankAtPromotion, full admiral]
-
A.
militaryRankBeforeAccession
Indicates the military rank held by an individual prior to their accession to a particular office, position, or status.
-
B.
militaryRankDate
Indicates the date on which an entity attained, held, or was recorded with a particular military rank.
-
C.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
D.
promotedToLieutenantGeneral
Indicates that an entity has been elevated in rank to the position of lieutenant general.
-
E.
militaryRankProgression
Indicates the sequence or advancement of an individual’s positions within a structured military rank hierarchy.
- F. None of above. chosen
Provenance (4 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:03 p.m.