Triple
T30307294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dokuganryū |
E770819
|
entity |
| Predicate | inspiredWorksAbout |
P62284
|
FINISHED |
| Object | Date Masamune |
—
|
NE NERFINISHED |
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: Date Masamune | Statement: [Dokuganryū, inspiredWorksAbout, Date Masamune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredWorksAbout Context triple: [Dokuganryū, inspiredWorksAbout, Date Masamune]
-
A.
inspiredWorks
Indicates that one work served as a source of inspiration or creative influence for the creation or development of another work.
-
B.
inspiredWorksOf
chosen
Indicates that one entity served as the source of inspiration or creative influence for the works produced by another entity.
-
C.
inspiredWorkAppearsOn
Indicates that a work created as a result of inspiration is featured, included, or presented on a particular medium, platform, or publication.
-
D.
inspiredArtist
Indicates that one artist has served as a source of creative influence or inspiration for another artist.
-
E.
inspiredBusinessOf
Indicates that one entity served as the inspiration or model for the business activities, practices, or creation of another entity.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 7:49 p.m.