Triple
T23829580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Around |
E589476
|
entity |
| Predicate | hasSignatureChant |
P15355
|
FINISHED |
| Object | Jump up, jump up and get down |
—
|
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: Jump up, jump up and get down | Statement: [Jump Around, hasSignatureChant, Jump up, jump up and get down]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureChant Context triple: [Jump Around, hasSignatureChant, Jump up, jump up and get down]
-
A.
hasChant
chosen
Indicates that an entity is associated with or characterized by a particular chant.
-
B.
hasSignatureSong
Indicates that an artist or performer is especially associated with a particular song that is widely recognized as their defining or most iconic work.
-
C.
hasSpokenChants
Indicates that an entity has uttered or recited ritualistic or formulaic chants, typically as part of a ceremonial, religious, or magical practice.
-
D.
hasSungChorus
Indicates that an entity has performed or participated in singing the chorus section of a song.
-
E.
hasChantLikeChorus
Indicates that one element features or is characterized by a chorus section that is chant-like in style or delivery.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f498c48190827e59df868c5cb1 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8 p.m.