Triple
T13160072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Nakajima |
E312700
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Nakajima |
E792995
|
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 | Statement: [Ken Nakajima, familyName, Nakajima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nakajima Context triple: [Ken Nakajima, familyName, Nakajima]
-
A.
Nakajima
chosen
Nakajima was a major Japanese aircraft manufacturer, especially active during World War II, known for producing numerous military aircraft for the Imperial Japanese Navy and Army.
-
B.
Nakajima Hikari
Nakajima Hikari is a Japanese politician who served as the successor to Nakajima Sakae 11 in public office.
-
C.
Nakajima Sakae
Nakajima Sakae is a Japanese individual whose specific public profile or notable achievements are not clearly identifiable from the available information.
-
D.
Yoshimura
Yoshimura is a Japanese surname borne by various notable individuals across fields such as politics, sports, and the arts.
-
E.
Mibuchi
Mibuchi is a Japanese surname borne by individuals such as Tadahiko Mibuchi.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c0971008190869e9de710f4c579 |
completed | April 10, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6eaf2ae688190b3484989791977ce |
completed | May 3, 2026, 6:28 a.m. |
Created at: April 9, 2026, 9:12 p.m.