Triple
T4341831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakajima Sakae 11 |
E97798
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Nakajima Sakae 21 |
E97798
|
NE 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: Nakajima Sakae 21 | Statement: [Nakajima Sakae 11, successor, Nakajima Sakae 21]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nakajima Sakae 21 Context triple: [Nakajima Sakae 11, successor, Nakajima Sakae 21]
-
A.
Nakajima Sakae 11
chosen
The Nakajima Sakae 11 was an early variant of Nakajima's air-cooled radial aircraft engine used in several Japanese military aircraft during the Second World War.
-
B.
Nakajima Hikari
Nakajima Hikari is a Japanese politician who served as the successor to Nakajima Sakae 11 in public office.
-
C.
Naikaku
Naikaku is the Japanese term for the Cabinet, the executive branch of Japan’s national government headed by the Prime Minister.
-
D.
AMAKUSA AIR
AMAKUSA AIR is the radio callsign used by Amakusa Airlines, a regional Japanese carrier serving routes primarily within Kyushu.
-
E.
Shibaura Futo
Shibaura Futo is a waterfront district and pier area in Tokyo’s Minato Ward, known for its views of Tokyo Bay and proximity to the Rainbow Bridge.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351878c148190b384053479d41caf |
completed | March 12, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5db9fd4988190afa9e04b029cd573 |
completed | March 14, 2026, 10:05 p.m. |
Created at: March 12, 2026, 11:14 p.m.