Triple

T1145940
Position Surface form Disambiguated ID Type / Status
Subject Imperial Regalia of Japan E23564 entity
Predicate mythologicalOrigin P9595 FINISHED
Object Japanese mythology 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 mythology | Statement: [Imperial Regalia of Japan, mythologicalOrigin, Japanese mythology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mythologicalOrigin
Context triple: [Imperial Regalia of Japan, mythologicalOrigin, Japanese mythology]
  • A. linkedToMythology chosen
    Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
  • B. mythologicalRole
    Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
  • C. mythologicalEvent
    Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
  • D. languageOfMyths
    Indicates that the subject is the language in which the myths associated with the object are told or recorded.
  • E. mythologicalLocation
    Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
  • 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc6e8c2081909fb3534413b7aacb completed March 1, 2026, 10:23 p.m.
PD Predicate disambiguation batch_69a4bb4d4104819084027a043c6118cb completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:44 p.m.