Triple
T8753023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Move On Up a Little Higher |
E208005
|
entity |
| Predicate | helpedBringGenreTo |
P70290
|
FINISHED |
| Object | wider audience |
—
|
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: wider audience | Statement: [Move On Up a Little Higher, helpedBringGenreTo, wider audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedBringGenreTo Context triple: [Move On Up a Little Higher, helpedBringGenreTo, wider audience]
-
A.
promotesGenre
chosen
Indicates that one entity actively supports, advertises, or increases the visibility of a particular genre.
-
B.
influencedByGenre
Indicates that something’s characteristics, style, or development are shaped or affected by a particular genre.
-
C.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
D.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
-
E.
genreIntroduced
Indicates that a particular genre was first introduced, originated, or came into existence at a specific time, place, or by a specific agent.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da8cc548190a31ad542d2faf2d5 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.