Triple
T25942770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzanne Verdal |
E653750
|
entity |
| Predicate | metLeonardCohenIn |
P159585
|
FINISHED |
| Object | Montreal |
—
|
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: Montreal | Statement: [Suzanne Verdal, metLeonardCohenIn, Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metLeonardCohenIn Context triple: [Suzanne Verdal, metLeonardCohenIn, Montreal]
-
A.
lyricallyPairedWith
Indicates that two musical or poetic elements are intentionally matched or combined in lyrics, such as being written to accompany each other or to form a complementary lyrical pair.
-
B.
الملحن
Indicates that an entity is the composer or creator of a musical work for another entity (such as a song, piece, or performance).
-
C.
singsAbout
Indicates that one entity performs a song whose subject or theme is another entity.
-
D.
hasWrittenLyricsFor
Indicates that one entity is the lyricist who has created the words for a song or musical work performed or associated with another entity.
-
E.
hasSongAbout
Indicates that one entity has created, features, or is associated with a song whose subject or theme is about another entity.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6045ec5708190917d60774389e68c |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:41 a.m.