Triple
T36132000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Concerto |
E1045046
|
entity |
| Predicate | hasLyricalWritingFor |
P184950
|
FINISHED |
| Object | clarinet |
—
|
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: clarinet | Statement: [Clarinet Concerto, hasLyricalWritingFor, clarinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricalWritingFor Context triple: [Clarinet Concerto, hasLyricalWritingFor, clarinet]
-
A.
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.
-
B.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
C.
hasLyricalLanguage
Indicates that something (such as a text or expression) employs poetic, expressive, or highly figurative language.
-
D.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
-
E.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.