Triple
T8456241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mujh Se Pehli Si Mohabbat |
E199925
|
entity |
| Predicate | writtenInMetre |
P82742
|
FINISHED |
| Object | nazm free-verse style |
—
|
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: nazm free-verse style | Statement: [Mujh Se Pehli Si Mohabbat, writtenInMetre, nazm free-verse style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenInMetre Context triple: [Mujh Se Pehli Si Mohabbat, writtenInMetre, nazm free-verse style]
-
A.
metre
Indicates a measurement relationship where one entity’s length, distance, or size is quantified in units of metres.
-
B.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
C.
dominantMetreOf
Indicates that one metre (rhythmic pattern) is the primary or prevailing metrical structure used in another work, passage, or musical/poetic context.
-
D.
typicalMeterInEnglish
Indicates that a given poetic meter is commonly or characteristically used in English verse.
-
E.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
- F. None of above. chosen
Provenance (4 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48e0ae481908b40f7f124b0551e |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:10 p.m.