Triple
T21887478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 玉依姫 |
E540442
|
entity |
| Predicate | 神話体系内の分類 |
P54299
|
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.
mythologicalCategory
chosen
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
B.
typeOfMythologicalGroup
Indicates that one entity is classified as a specific kind or category of mythological group to which the other entity belongs.
-
C.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
D.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
E.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.