Triple
T33201641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachchai Nirame |
E849913
|
entity |
| Predicate | creditedSinger |
P81375
|
FINISHED |
| Object | Hariharan |
—
|
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: Hariharan | Statement: [Pachchai Nirame, creditedSinger, Hariharan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditedSinger Context triple: [Pachchai Nirame, creditedSinger, Hariharan]
-
A.
creditedMusician
Indicates that a musician is formally acknowledged as having contributed to a particular musical work or recording.
-
B.
isSingerFrom
Indicates that a person is a singer who originates from or is associated with a particular place or region.
-
C.
isSungBy
chosen
Indicates that a song, piece of music, or vocal performance is performed vocally by a particular singer or group of singers.
-
D.
hasSongwriterWithUnverifiedCredit
Indicates that an entity is associated with a songwriter whose authorship credit exists but has not been fully verified or confirmed.
-
E.
creditedFor
Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.