Triple
T3090227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohri |
E64462
|
entity |
| Predicate | featuresMusic |
P5483
|
FINISHED |
| Object | Punjabi folk songs |
—
|
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: Punjabi folk songs | Statement: [Lohri, featuresMusic, Punjabi folk songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMusic Context triple: [Lohri, featuresMusic, Punjabi folk songs]
-
A.
featuresMusician
Indicates that something (such as a work, event, or recording) prominently includes or showcases a particular musician.
-
B.
musicElement
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
-
C.
musicBy
Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
-
D.
genreFeatures
chosen
Indicates that a particular genre is characterized or defined by certain features or attributes.
-
E.
musicFusionOf
Indicates a relationship where one musical work, style, or element is created by combining or blending two or more distinct musical sources or genres.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20d8f788190b05b8b6b5042bc1a |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.