Triple
T105706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimigayo |
E2131
|
entity |
| Predicate | hasRecordingType |
P2554
|
FINISHED |
| Object | orchestral arrangement |
—
|
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: orchestral arrangement | Statement: [Kimigayo, hasRecordingType, orchestral arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingType Context triple: [Kimigayo, hasRecordingType, orchestral arrangement]
-
A.
hasRecordType
chosen
Indicates that an entity is associated with or classified under a specific type or category of record.
-
B.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
C.
hasRecreationType
Indicates that an entity is associated with or offers a particular type or category of recreational activity.
-
D.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
E.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
- 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.