Triple
T19258041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump to the Beat |
E481568
|
entity |
| Predicate | hasPerformerAgeRangeAtRelease |
P79821
|
FINISHED |
| Object | teenage |
—
|
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: teenage | Statement: [Jump to the Beat, hasPerformerAgeRangeAtRelease, teenage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerAgeRangeAtRelease Context triple: [Jump to the Beat, hasPerformerAgeRangeAtRelease, teenage]
-
A.
performerAgeAtRelease
chosen
Indicates the age of a performer at the time a work (such as a recording or performance) is released.
-
B.
hasPerformerBirthYear
Indicates that a performer is associated with a specific year in which they were born.
-
C.
performerAgeAtRecording
Indicates the age of the performer at the time the recording was made.
-
D.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
E.
workReleaseYear
Indicates the calendar year in which a work (such as a book, film, or album) was first released or made publicly available.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8752488190ae2dfd2d79373a4b |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.