Triple
T27858370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Train |
E704147
|
entity |
| Predicate | isMostSuccessfulSoloHitOf |
P163740
|
FINISHED |
| Object | Holly Johnson |
E186264
|
NE 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: Holly Johnson | Statement: [Love Train, isMostSuccessfulSoloHitOf, Holly Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMostSuccessfulSoloHitOf Context triple: [Love Train, isMostSuccessfulSoloHitOf, Holly Johnson]
-
A.
isBsideToHitSingle
Indicates that one song serves as the B-side track accompanying another song that is a hit single.
-
B.
firstSuccessfulImpactBy
Indicates that one entity is the earliest or initial successful impactor upon another entity in a given context or sequence of events.
-
C.
hitSingle
Indicates that a batter successfully hits the ball and reaches first base safely, recording a single.
-
D.
isMajorHit
Indicates that something (such as a work, product, or performance) has achieved a high level of success, popularity, or impact.
-
E.
wasAHitIn
Indicates that something (such as a work, product, or performance) achieved notable success or popularity within a specified context, time period, or location.
- F. None of above. chosen
Provenance (5 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1632de40f08190aa5dd3942c661d90 |
completed | May 26, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:16 p.m.