Triple
T19033280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billy Flynn |
E465798
|
entity |
| Predicate | catchphraseLyric |
P74838
|
FINISHED |
| Object | All I care about is 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: All I care about is love | Statement: [Billy Flynn, catchphraseLyric, All I care about is love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catchphraseLyric Context triple: [Billy Flynn, catchphraseLyric, All I care about is love]
-
A.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
B.
featuresCatchphrase
Indicates that an entity prominently includes or is associated with a particular catchphrase.
-
C.
typicalPhrase
Indicates that the object is a phrase commonly or characteristically used in connection with the subject.
-
D.
hasCatchphraseStyle
Indicates that an entity’s catchphrase conforms to, or is characterized by, a particular stylistic pattern or manner of expression.
-
E.
characterCatchphrase
chosen
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d741cabc8190900e12265ad269f8 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.