Triple
T247035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jana Gana Mana |
E5059
|
entity |
| Predicate | commonlySungPortion |
P1147
|
FINISHED |
| Object | first stanza |
—
|
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: first stanza | Statement: [Jana Gana Mana, commonlySungPortion, first stanza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlySungPortion Context triple: [Jana Gana Mana, commonlySungPortion, first stanza]
-
A.
commonlySungStanzas
chosen
Indicates that certain stanzas of a song or poem are those most frequently sung or performed in practice.
-
B.
isSignatureSongOf
Indicates that a particular song is widely recognized as the most iconic or defining song associated with a specific artist or group.
-
C.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
D.
hasSignatureSong
Indicates that an artist or performer is especially associated with a particular song that is widely recognized as their defining or most iconic work.
-
E.
hasSpecialSong
Indicates that one entity possesses or is associated with a particular song that is unique, distinctive, or specially designated for 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d13b8088190a3f48f0388d57496 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.