Triple
T13271388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syusen |
E316064
|
entity |
| Predicate | hasNATOReportingName |
P6062
|
FINISHED |
| Object | Syusen |
E316064
|
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: Syusen | Statement: [Syusen, hasNATOReportingName, Syusen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Syusen Context triple: [Syusen, hasNATOReportingName, Syusen]
-
A.
Syusen
chosen
Syusen is the NATO reporting name for the Mitsubishi J8M, a World War II-era Japanese rocket-powered interceptor aircraft.
-
B.
Shinshisha
Shinshisha was a pioneering early 20th-century Japanese literary coterie and poetry magazine circle known for promoting innovative tanka poetry and modernist literature.
-
C.
Shisō
Shisō is a city in Hyōgo Prefecture, Japan, known for its rural landscapes, forests, and historical sites.
-
D.
Shinsen
Shinsen is a neighborhood in Tokyo’s Shibuya ward known for its residential streets, local eateries, and proximity to the bustling Shibuya Station area.
-
E.
Tokusuke
Tokusuke is the given name of Nakae Chōmin, a prominent Japanese political theorist, journalist, and early advocate of liberal democracy in the Meiji era.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99020f710819094c2618662bdc7fd |
completed | April 11, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a4e98888190af5cb857b2437f09 |
completed | May 3, 2026, 8:41 a.m. |
Created at: April 9, 2026, 9:26 p.m.