Triple
T105677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimigayo |
E2131
|
entity |
| Predicate | hasLyricist |
P1141
|
FINISHED |
| Object | unknown classical Japanese poet |
—
|
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: unknown classical Japanese poet | Statement: [Kimigayo, hasLyricist, unknown classical Japanese poet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricist Context triple: [Kimigayo, hasLyricist, unknown classical Japanese poet]
-
A.
lyricist
Indicates that one entity is the writer of the words (lyrics) for a musical work associated with another entity.
-
B.
lyricsBy
chosen
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
C.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
D.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
E.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a256ec650c8190bee2067e37065527 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563d33788190999d471b486d5603 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.