Triple
T30692899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Again |
E781377
|
entity |
| Predicate | hasChartAppeal |
P193129
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Love Again, hasChartAppeal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChartAppeal Context triple: [Love Again, hasChartAppeal, true]
-
A.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
B.
hasMassAppeal
Indicates that something possesses qualities or characteristics that attract or are appealing to a very large, broad, or general audience.
-
C.
handledAppeals
Indicates that one party has received, reviewed, and taken action on appeals submitted by another party.
-
D.
hasCrossoverAppeal
Indicates that something attracts or appeals to multiple distinct groups, genres, or audiences beyond its original or primary category.
-
E.
hasEnduringAppeal
Indicates that something continues to attract interest, admiration, or enjoyment over a long period of time.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:33 p.m.