Triple
T3130198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PJ |
E65390
|
entity |
| Predicate | collaborationRole |
P15464
|
FINISHED |
| Object | featured artist |
—
|
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: featured artist | Statement: [PJ, collaborationRole, featured artist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationRole Context triple: [PJ, collaborationRole, featured artist]
-
A.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
notableWorkRole
chosen
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
C.
primaryCollaborator
Indicates that one entity serves as the main or most significant partner working jointly with another entity on a shared activity, project, or goal.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada549aaa881908dcf92d20fa6f238 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.