Triple
T12614025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamo Tamayori-hime no Mikoto |
E301204
|
entity |
| Predicate | hasOffspringType |
P25956
|
FINISHED |
| Object | thunder deity |
—
|
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: thunder deity | Statement: [Kamo Tamayori-hime no Mikoto, hasOffspringType, thunder deity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOffspringType Context triple: [Kamo Tamayori-hime no Mikoto, hasOffspringType, thunder deity]
-
A.
offspringType
chosen
Indicates the specific kind or category of offspring that results from a parent or reproductive event.
-
B.
offspringWith
Indicates that two entities share a parent–child relationship, specifying that one is the offspring of the other.
-
C.
hasReproductionType
Indicates the mode or method by which an entity reproduces or generates offspring.
-
D.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
E.
hasNotableSuccessorType
Indicates that an entity has a successor whose type or category is considered notably significant or distinguished in relation to it.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.