Triple
T22486695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Climb to Safety |
E555902
|
entity |
| Predicate | primaryPerformerType |
P85537
|
FINISHED |
| Object | American jam band |
—
|
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: American jam band | Statement: [Climb to Safety, primaryPerformerType, American jam band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPerformerType Context triple: [Climb to Safety, primaryPerformerType, American jam band]
-
A.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
primaryArtist
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
C.
typicalPerformerRoleType
chosen
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
D.
originalPerformerGenre
Indicates that a performer is originally associated with or primarily known for a particular musical or artistic genre.
-
E.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3da9588190abf2f96d3104edfb |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.