Triple
T35478917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Love |
E1025414
|
entity |
| Predicate | firstTelevisedPerformance |
P58338
|
FINISHED |
| Object | Top of the Pops |
E432031
|
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: Top of the Pops | Statement: [Hot Love, firstTelevisedPerformance, Top of the Pops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTelevisedPerformance Context triple: [Hot Love, firstTelevisedPerformance, Top of the Pops]
-
A.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
B.
firstOfficialPerformance
Indicates that an event is the earliest formally recognized performance or presentation by a particular entity (such as an artist, group, or production).
-
C.
firstPerformanceAt
chosen
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
D.
firstPerformanceProduction
Indicates that a production is the one in which a work (e.g., a play, musical, or performance piece) was first publicly performed.
-
E.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
- F. None of above.
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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38403daba0819096a88a4b90ae4fe5 |
completed | June 21, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.