Triple
T38085982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eiroku 3 |
E950977
|
entity |
| Predicate | eraNameKanji |
P114914
|
FINISHED |
| Object | 永禄 |
—
|
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: 永禄 | Statement: [Eiroku 3, eraNameKanji, 永禄]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNameKanji Context triple: [Eiroku 3, eraNameKanji, 永禄]
-
A.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
-
B.
nameInJapaneseKana
Indicates that an entity’s name is written or represented using Japanese kana characters.
-
C.
hasNameInKanji
chosen
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
-
D.
JapaneseNameOrigin
Indicates that one entity’s name originates from or is derived from the Japanese language or naming tradition in relation to another entity.
-
E.
formerJapaneseNameOf
Indicates that one entity was previously used as the Japanese name for another entity but is no longer its current Japanese name.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.