Triple
T14358890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fatale |
E356042
|
entity |
| Predicate | hasCreatorCollaboration |
P60681
|
FINISHED |
| Object | Brubaker–Phillips collaborations |
—
|
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: Brubaker–Phillips collaborations | Statement: [Fatale, hasCreatorCollaboration, Brubaker–Phillips collaborations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatorCollaboration Context triple: [Fatale, hasCreatorCollaboration, Brubaker–Phillips collaborations]
-
A.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
B.
hasCollaboratedIn
chosen
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
D.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
E.
hasCreatorRoleFor
Indicates that an entity serves in the role of creator for another entity, establishing a creator-to-created relationship.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f52ca7881908704eef20228aed3 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:15 a.m.