Triple
T25021046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 高天原 |
E626568
|
entity |
| Predicate | 神話上の出来事 |
P2288
|
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: [高天原, 神話上の出来事, 天岩戸隠れの舞台]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 神話上の出来事 Context triple: [高天原, 神話上の出来事, 天岩戸隠れの舞台]
-
A.
mythologicalEvent
chosen
Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
-
B.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
D.
depictsMythologicalEvent
Indicates that one entity visually represents or portrays a mythological event involving gods, heroes, or legendary occurrences.
-
E.
hasMythologicalBasis
Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44ba9d564819087d3b9041bb0205b |
completed | May 1, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:06 a.m.