Triple
T28025387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rikugun-shō |
E707806
|
entity |
| Predicate | Kaigun-shōIs |
P163636
|
FINISHED |
| Object | Ministry of the Navy of Imperial Japan |
—
|
NE NERFINISHED |
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: Ministry of the Navy of Imperial Japan | Statement: [Rikugun-shō, Kaigun-shōIs, Ministry of the Navy of Imperial Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Kaigun-shōIs Context triple: [Rikugun-shō, Kaigun-shōIs, Ministry of the Navy of Imperial Japan]
-
A.
lastShogun
Indicates that the subject is the final individual to hold the position or title of shogun in a given historical or organizational context.
-
B.
namesakeShip
Indicates that one entity is a ship that is named after, or serves as the namesake of, another entity.
-
C.
Juyo
Indicates a relationship where one entity is associated with or characterized by the concept or style referred to as "Juyo."
-
D.
shogunateName
Indicates the name assigned to a particular shogunate.
-
E.
ichinomiya
Indicates a relationship where a location or institution holds the status of "Ichinomiya," the primary or highest-ranking Shinto shrine of a historical province.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c6d6a48819096c6076323dc45a6 |
completed | May 2, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:12 p.m.