Triple
T17972182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakajima B6N Tenzan |
E449372
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Tenzan |
—
|
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: Tenzan | Statement: [Nakajima B6N Tenzan, alsoKnownAs, Tenzan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tenzan Context triple: [Nakajima B6N Tenzan, alsoKnownAs, Tenzan]
-
A.
Tenzan
chosen
Tenzan is a Japanese term meaning "Heavenly Mountain," commonly used as a name for mountains, locations, and cultural references in Japan.
-
B.
Hyakutake
Hyakutake is a Japanese surname borne by several notable individuals, including military figures and other public personalities.
-
C.
Gokenzan
Gokenzan is the mountain in Kagawa Prefecture on which Temple 84, Yashimaji, of the Shikoku Pilgrimage is located.
-
D.
Ōyama
Ōyama is a Japanese surname borne by various notable figures in Japan’s military, political, and cultural history.
-
E.
Daisen
Daisen is a city in Japan known for its location in Akita Prefecture and its rich agricultural and cultural traditions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fb58c481909726d6f916f6f646 |
completed | April 19, 2026, 10:44 a.m. |
Created at: April 10, 2026, 10:22 a.m.