Triple
T21237822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamuyamato Iwarebiko |
E523390
|
entity |
| Predicate | typeOfLegend |
P122936
|
FINISHED |
| Object | foundation myth |
—
|
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: foundation myth | Statement: [Kamuyamato Iwarebiko, typeOfLegend, foundation myth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLegend Context triple: [Kamuyamato Iwarebiko, typeOfLegend, foundation myth]
-
A.
inLegendRole
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
B.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
C.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
D.
legendStatus
chosen
Indicates that an entity holds, is assigned, or is associated with a particular legend-related status or classification.
-
E.
originLegendSource
Indicates that a legend or traditional story about an entity originates from, or is sourced in, a particular place, culture, or narrative 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735212ad4819082d85f4d4342faf9 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:46 p.m.