Triple
T1302769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higher Truth |
E27803
|
entity |
| Predicate | artistRole |
P24740
|
FINISHED |
| Object | Soundgarden frontman |
—
|
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: Soundgarden frontman | Statement: [Higher Truth, artistRole, Soundgarden frontman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artistRole Context triple: [Higher Truth, artistRole, Soundgarden frontman]
-
A.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
B.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
-
C.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
D.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
E.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c115ba64819081c55fa6807e19ef |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.