Triple
T31107208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toho Co., Ltd. |
E792825
|
entity |
| Predicate | languageOfOriginForGodzillaName |
P38935
|
FINISHED |
| Object | Japanese |
—
|
LITERAL 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: Japanese | Statement: [Toho Co., Ltd., languageOfOriginForGodzillaName, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfOriginForGodzillaName Context triple: [Toho Co., Ltd., languageOfOriginForGodzillaName, Japanese]
-
A.
eraOfGodzillaSeries
Indicates the specific historical or thematic period within the Godzilla franchise to which a given work or entry belongs.
-
B.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
-
C.
relationshipWithGodzilla
Indicates the type or nature of a relationship that an entity has with Godzilla.
-
D.
positionInGodzillaSeries
Indicates the specific installment number or order that an item occupies within the Godzilla series.
-
E.
JapaneseNameOrigin
chosen
Indicates that one entity’s name originates from or is derived from the Japanese language or naming tradition in relation to another entity.
- F. None of above.
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: April 29, 2026, 9:03 p.m.