Triple
T22093468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Maivia |
E545964
|
entity |
| Predicate | heritageOfPerformer |
P119106
|
FINISHED |
| Object | Samoan |
—
|
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: Samoan | Statement: [Rocky Maivia, heritageOfPerformer, Samoan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageOfPerformer Context triple: [Rocky Maivia, heritageOfPerformer, Samoan]
-
A.
associatedWithArtistHeritage
chosen
Indicates a relationship where an entity is connected to, derived from, or meaningfully linked with an artist’s cultural, ethnic, or historical heritage.
-
B.
musicLegacy
Indicates how an entity’s influence, contributions, or style continue to shape or be remembered in music beyond its original time or context.
-
C.
performerNotableWork
Indicates that a performer is significantly associated with or best known for a particular work (such as a performance, production, or recording).
-
D.
performerOrigin
Indicates that a performer originates from, or is associated with, a particular place or region.
-
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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e766388190aad1039fe0849771 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.