Triple
T29891946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Light Music |
E759173
|
entity |
| Predicate | shortFormOfAssociatedPerson |
P99167
|
FINISHED |
| Object | M. S. Viswanathan |
—
|
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: M. S. Viswanathan | Statement: [King of Light Music, shortFormOfAssociatedPerson, M. S. Viswanathan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortFormOfAssociatedPerson Context triple: [King of Light Music, shortFormOfAssociatedPerson, M. S. Viswanathan]
-
A.
shortFormType
Indicates that one entity is a shortened, abbreviated, or otherwise condensed form or variant of another entity.
-
B.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
C.
associatedPersonField
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
-
D.
commonShortNameFor
chosen
Indicates that one entity is a commonly used short or abbreviated name for another entity.
-
E.
bearerShortName
Indicates that an entity serves as the short or abbreviated name used to identify the bearer in the context of a relationship or action.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6770137bc819082b1903f8a8dc8dc |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:03 p.m.