Triple
T28275474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Wouldn’t Normally Do This Kind of Thing |
E712975
|
entity |
| Predicate | hasLyricalTopic |
P4921
|
FINISHED |
| Object | falling in love |
—
|
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: falling in love | Statement: [I Wouldn’t Normally Do This Kind of Thing, hasLyricalTopic, falling in love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricalTopic Context triple: [I Wouldn’t Normally Do This Kind of Thing, hasLyricalTopic, falling in love]
-
A.
hasLyricalTheme
chosen
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
B.
hasLyricsTheme
Indicates that the lyrics of a work primarily concern or revolve around a specified theme or subject.
-
C.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
D.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
E.
hasLyricsMentioning
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6444b5f288190b5c6ed6340b83427 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:20 p.m.